- Rating
- 1
- Confidence
- 4
- Informativeness
- 2
- Presentation
- 3
- Soundness
- 1
Read review
Paper summary
The paper presents an approach to discover failure modes in agentic AI systems. The framework consists of four stages, namely, Failure Case Canonicalization that uses LLM judge to produce a concise error summary from the failure traces, Coarse-Grained Failure Pattern Induction for clustering those canonical failures using LLMs, Auto-stop Hierarchical Refinement for recursively refining the failure cluster into sub-clusters using LLMs, and Statistical Validation that generates synthetic test cases for each of the sub-clusters at the leaf level and conducts A/B hypothesis testing against a baseline success rate to identify statistically significant failure modes. Further, mitigation is conducted in two ways, using Claude Opus 4.6 and human refinement. The framework is primarily tested with a conversational multi-agent system with a synthetically generated user simulator and test cases for customer service. Results show that the pipeline helps improve the success rate from 74.9% to 85.3%.
Critical strengths
- The framework is practically useful and works even without historical trajectories. It provides failure categories, helps identify statistically significant failure modes, and automated mitigation.
- The framework is general as demonstrated by applying it to -bench agents.
- Results show that the overall framework helps improve task success on customer service tasks.
Critical weaknesses
- No baseline comparison against existing error attribution or failure mitigation work. The abstract claims that the framework identifies failure modes missed by capability benchmarks and LLM judge-based evaluation approaches but this is not supported by results.
- The first three stages in the pipeline are LLM-based. It would help to add accuracy (e.g., precision, recall) of each stage. There is some lightweight review of failures as stated in Appendix N but no details about the rigor of the human validation process is provided.
- The results are based on a single run of a single model. As stated in the paper, there is high level of uncertainty by changing the model. Thus, it would help to see results consistently improve over multiple runs and generalize across models.
Questions for authors
- How are the n=100 test cases generated? Are they targeted to try to test the particular failure category? Then, for the newly generated traces, do you re-label if the same failure occurs or just any failure?
- What is the error distribution after mitigation strategies are applied?