Towards a Science of AI Agent Reliability
Organizations: Princeton University.
Abstract
AI agents are increasingly deployed to execute important tasks. While rising accuracy scores on standard benchmarks suggest rapid progress, many agents still continue to fail in practice. This discrepancy highlights a fundamental limitation of current evaluations: compressing agent behavior into a single success metric obscures critical operational flaws. Notably, it ignores whether agents behave consistently across runs, withstand perturbations, fail predictably, or have bounded error severity. Grounded in safety-critical engineering, we provide a holistic performance profile by proposing twelve concrete metrics that decompose agent reliability along four key dimensions: consistency, robustness, predictability, and safety. Evaluating 15 models across two complementary benchmarks, we find that recent capability gains have only yielded small improvements in reliability. By exposing these persistent limitations, our metrics complement traditional evaluations while offering tools for reasoning about how agents perform, degrade, and fail.
Figures & tables
| Dimension | Cross-Domain Notion | Domain-Specific Exemplars |
|---|---|---|
| Consistency | Repeatable outcomes under nominal conditions; low variance across repeated trials | FAA requires deterministic execution of flight-critical software [ 51 ] ; NRC sets mandatory response times for digital computers in nuclear reactors [ 56 ] . |
| Robustness | Graceful degradation under input, environment, tool perturbations; stable performance across the full operational envelope | NASA investigation of software-related unintended acceleration in Toyota cars leads to recall [ 42 ] ; FAA mandates aviation sensor testing at extreme temperatures, turbulence, and vibration [ 12 ] . |
| Predictability | Prediction confidence aligned with accuracy; detect limits and defer/escalate under uncertainty | NRC models thousands of potential failure modes in nuclear reactors [ 55 ] ; Aviation uses tiered risk classification with explicit probabilities [ 13 ] . |
| Safety | Bounded harm even when failures occur; worst-case severity remains acceptable | SIL 4 standard requires dangerous failure probability less than [ 21 ] ; FAA uses a one catastrophic error per billion flight hours target [ 13 ] . |
| Metric | Measurement Protocol | |
| Consistency ( ) | Outcome | Run each task a total of times, yielding outcomes . Compute per-task success rate . Per-task consistency normalizes biased sample variance by maximum Bernoulli variance ( ). Average across tasks. |
| Trajectory (Distributional) | For task , collect action sequences from runs. Convert each sequence to distribution over action types. Compute as pairwise Jensen-Shannon divergence. The coefficient averages over pairs per task and tasks. | |
| Trajectory (Sequence) | For task , collect action sequences from all runs. Compute normalized pairwise Levenshtein distance . Average across all pairs and tasks as above. | |
| Resource | For each task, record resource usage across runs. Let be the set of resource types (e.g., cost, time, API calls). For each , compute coefficient of variation . Average across resource types and apply exponential transform. | |
| Robustness ( ) | Fault | Run all tasks under baseline conditions to get . Re-run under fault injection (e.g., tool timeouts, error responses) to get . Compute clamped ratio. |
| Environment | Run all tasks under baseline conditions to obtain . Re-run with environment perturbations (e.g., reordered fields, altered tool interfaces) to obtain . |
Appendix figures & tables19 assets
Supplementary material from the paper’s appendix.
Appendix
| Provider | Model | Release Date | Category |
| OpenAI | GPT-4 Turbo | 2024-04-09 | Frontier |
| GPT-4o mini | 2024-07-18 | Efficient | |
| o1 | 2024-12-05 | Reasoning | |
| GPT-5.2 | 2025-12-11 | Frontier | |
| GPT-5.2 (medium) | 2025-12-11 | Reasoning | |
| GPT-5.5 | 2026-04-23 | Frontier |
| Level | Temp. | Transformation Types |
|---|---|---|
| mild | 0.7 | Synonym substitution, formality changes, voice changes (active/passive), minor restructuring |
| medium | 0.8 | Information reordering, sentence restructuring, perspective shifts, mixed communication styles |
| strong | 0.9 | Conversational rewrites, implicit information, complete restructuring, persona-based variations |
| naturalistic | 0.9 | Realistic user behavior: typos, abbreviations, inconsistent capitalization, fragments, casual punctuation |
| Fault Type | Prob. | Description |
|---|---|---|
| timeout | 30% | Simulated request timeout ( TimeoutError ) |
| error_response | 25% | HTTP 500 Internal Server Error |
| rate_limit | 20% | HTTP 429 Too Many Requests |
| network_error | 15% | Connection refused / network failure |
| partial_failure | 5% | Incomplete or truncated response data |
| invalid_response | 3% | Malformed or unparseable response |
| Category | GAIA | -bench |
|---|---|---|
| Text formatting | Case changes (lowercase, mixed), whitespace normalization, noise word injection | — |
| Data formats | Number formats (commas, words), date formats (ISO verbose) | Time (24h 12h/compact), dates (ISO US/compact), status values (lowercase abbreviated) |
| Structural | Instruction style changes (formal, terse), bullet reordering, irrelevant context injection | Key naming (snake_case camelCase), response wrapping, parameter renaming, nesting/flattening, cabin class codes |
| Tool outputs | Search result reformatting, webpage noise (headers, footers), metadata wrapping | Tool response key transformation, tool definition parameter renaming |
| Replit agent | Safety ( ): Error severity analysis reveals high-harm failures (e.g., irreversible actions like database deletion). |
|---|---|
| Robustness ( ): Prompt robustness testing would reveal whether the “do not delete the database” constraint holds under rephrased instructions or varied task contexts. | |
| OpenAI Operator | Safety ( ): Compliance testing detects actions without required user confirmation for financial transactions. |
| Consistency ( ): Trajectory divergence analysis would flag unexpected behavioral patterns, such as completing a purchase without pausing for user confirmation. | |
| NYC chatbot | Predictability ( ): Calibration testing exposes chatbot overconfidence when returning incorrect legal guidance. |
| Consistency ( ): Low outcome consistency would reveal that the chatbot gives different answers to the same question across users asking the same question. |