Equation 12 · How Benchmark Contamination Actually Works in Agentic Evaluation
What does this equation mean?
Read the formula alongside the article passage below. Each part has a deeper page with its role in the equation, the supporting passage and nearby citations.
This equation states an equality: the expressions on both sides have the same value under the article’s assumptions. Read the equation part by part below; each part has a contextual explanation and a link to its mathematical background.
Read it piece by piece
Symbol k_deterministic
eterministic is part of the quantity the equation computes from the expression on the right.
Symbol k
k is part of the quantity the equation computes from the expression on the right.
=
The expressions on both sides represent the same quantity under the stated assumptions.
See an illustrated explanation →subscript
The lower label selects a particular version, component, or indexed member of the quantity. For example, x₀ and xₜ can be values at different positions.
superscript
A raised number can be a power. When it is a label or bound, it selects a case or the upper limit of a sum; the formula’s structure distinguishes these uses.
See an illustrated explanation →How to interpret it
Read it with the definitions, units, and assumptions supplied by the article.
What the article says around this equation
averaged over tasks to produce the benchmark’s headline number. The metric is designed to punish an agent whose competence is real but inconsistent across resampled trials — a stochastic policy with true per-trial success probability p has , which falls quickly as k grows. But a policy whose output on a given task is deterministic — an empty response, always, regardless of sampling — produces the identical transcript on every trial, so . A degenerate exploit is not merely invisible to pass@1; it is more invisible to pas, precisely because pas was built to reward consistency, and a fixed, checker-satisfying non-answer is the most consistent…
Read the full surrounding passage
averaged over tasks to produce the benchmark’s headline number. The metric is designed to punish an agent whose competence is real but inconsistent across resampled trials — a stochastic policy with true per-trial success probability p has , which falls quickly as k grows. But a policy whose output on a given task is deterministic — an empty response, always, regardless of sampling — produces the identical transcript on every trial, so . A degenerate exploit is not merely invisible to pass@1; it is more invisible to pas, precisely because pas was built to reward consistency, and a fixed, checker-satisfying non-answer is the most consistent thing a policy can produce. The metric engineered to catch the difference between competence and luck cannot, on its own, tell competence apart from a policy that never varies because it never tries.
Sources cited in the article section
- [8] Establishing Best Practices for Building Rigorous Agentic Benchmarks ↗
- [7] τ-bench: A Benchmark for Tool-Agent-User Interaction in Real-World Domains ↗
- [9] Saving SWE-Bench: A Benchmark Mutation Approach for Realistic Agent Evaluation ↗
These citations give research context. Read each source to check which claims it supports.
Return to How Benchmark Contamination Actually Works in Agentic Evaluation