When Agent Evaluation Becomes Unreliable: An Empirical Study of Oracle Failures and Configuration-Dependent Measurement in an LLM Agent Benchmark
Organizations: School of Computer Science and Engineering, Nanjing University of Science and Technology, Nanjing, China.
Abstract
Agent evaluation harnesses are software: they run a test suite, drive a test input generator, and decide outcomes with a test oracle. We audit them for defects a score table cannot show. First, a systematic oracle-integrity auditing approach - five state-integrity invariants and three known-answer controls - is measured by injecting seven oracle defect classes across two task domains and a synthetic domain. Every class is detected, and on the 57 separable variant-target combinations it detects 54; the repaired oracle yields no false positive. On a widely used agent benchmark, it exposes a reward function that resets the database to build a ground-truth hash and never restores it, so a harness scoring afterwards reads the reference solution's state: recorded labels report 4,194 database passes over 4,320 episodes, replay gives 2,883, and success falls from 94.3% to 65.5%. The correction is not a uniform offset; it removes 24 to 34 points from each agent and changes which agent this matrix measures as strongest. Second, more weakly, localising the apparatus is a property of the measurement: a 3,240-episode ablation associates the three documents with lower collapse in the tested configuration, without ordering them, and a second task domain reverses the language effect. Third, the method did not transfer to a second, independently implemented benchmark; we name the contract required. A replication package recomputes every analysis offline with no model calls.
Figures & tables
| Study | Object audited | Evidence produced | Not tested |
|---|---|---|---|
| Gao & Zhou (2026) | completed run records against the reported score | three-state evidence label and score bounds | the oracle’s state behaviour; detection under injected defects |
| Bellibatlu et al. (2026) | documented tool contract against the implementation | contract violations, per tool | the reward function and its integration with the harness |
| This paper | the oracle and its integration with the harness | state invariants, known-answer controls, a 21-variant battery over three targets, and a replay-based correction | whether the stored evidence behind a score is sufficient |
| Analysis (section) | Frozen source | Entry point | Recomputed offline |
|---|---|---|---|
| Archived and corrected labels; main matrix (§ 4.1 ) | v1.0 archive | bash scripts/ offline_repro.sh | yes: per-episode records, replay and corrected labels; no model client, no key, no network |
| Oracle-integrity matrix; component ablation; cross-domain experiment; adjudication statistics (§ 4.1 –§ 4.3 ) | S2 archive | cd sqj && bash swe/reproduce_s2.sh | yes for the matrices, intervals and agreement statistics; the adjudicator’s verdicts are archived, not re-queried |
| Fault battery; detector ablations; power analysis; portability attempt (§ 4.1 , § 6 ) | enhancement archive | bash checks/ clean_room.sh <S2 root> | yes with the S2 archive present; the AppWorld probes are not reproducible and its task data is not distributed |
| Label transition and agent comparison (§ 4.1 ; added in v2) | v1.0 archive and its released replay table | python3 v2_01_ label_transition.py and v2_02_agent_gaps.py (v2 analysis package) | yes: deterministic from the archived labels and the replay |
| Defect class | separable comb. | checks that fire | necessary |
|---|---|---|---|
| state mutation | 9 | INV - 1 , INV - 2 , INV - 4 , INV - 5 , CTL - 1 , CTL - 2 | CTL - 1 |
| exception leak | 9 | INV - 1 , INV - 2 , INV - 4 , INV - 5 , CTL - 2 , CTL - 3 | INV - 4 |
| actions not restored | 9 | INV - 1 , INV - 2 , INV - 4 , INV - 5 | none |
| order dependence | 9 | INV - 3 | INV - 3 |
| saturated oracle | 9 | CTL - 1 | CTL - 1 |
| database-blind oracle | 7 | CTL - 1 | CTL - 1 |
| Agent | Archived | Corrected | pp [95% CI] | Rank (arch.) | Rank (corr.) |
|---|---|---|---|---|---|
| DeepSeek-V4.1-Flash | 98.0% | 64.4% | 1 | 3 | |
| Qwen3.7-Plus | 97.7% | 73.1% | 2 | 1 | |
| Qwen3.8-Max | 95.9% | 71.9% | 3 | 2 | |
| Qwen3.8-Flash | 85.6% | 52.5% | 4 | 4 | |
| Pooled | 94.3% | 65.5% | — | — |
| Arm | Collapse | collapse | success |
|---|---|---|---|
| English baseline | 9.81% (106/1080) | — | — |
| Tool descriptions Chinese | 0.65% (7/1080) | ||
| Chinese environment (all three) | 1.76% (19/1080) | ||
| Chinese length padding | 1.30% (14/1079) | ||
| Policy Chinese | 2.59% (28/1080) | ||
| Error strings Chinese | 4.54% (49/1080) |
Benchmark Auditing
Benchmark auditing checks whether evaluation datasets, metrics, and infrastructure measure the capabilities and risks they claim to assess.
See all 97 papers