- Rating
- 3
- Confidence
- 3
- Informativeness
- 2
- Presentation
- 2
- Soundness
- 2
Read review
Paper summary
The paper studies when tool failures make LLM agents give confident wrong answers. It builds a testbed (QuietFail) where each faulty run has a matching fault-free run. The main finding: errors like "permission denied" mostly lead to honest failure, but a tool that silently returns half the data leads to many confident wrong answers. Adding a short notice ("showing k of n rows") removes most of this, and a cursor to fetch the rest restores correct answers.
Critical strengths
- Clean design and a clear, useful message. Pairing every fault with a fault-free run, and grouping faults by what the tool returns, makes the main effect easy to see. The advice for tool builders (say when you truncate, say how much, give a way to get the rest) is simple and practical.
- Careful checks and real-world link. The authors test their results with a second judge, a rule-based grader and task-level bootstrap. The audit of 87 real tool surfaces shows the problem is common in shipped tools.
Critical weaknesses
- Small and simple tasks. Most claims rest on 21 tasks with tiny data (e.g., 3 of 6 rows dropped) and one fault per run. Two of the four main tests are not significant at task level, and the main tests were chosen after the data was analyzed. The most common real case in their audit (top-k results) is not tested.
- Grading and data collection issues. One LLM judge, from the same family as several agents, does most of the grading, and there is no human annotation. The rule-based grader gives effects only a third to nine-tenths as large. Seven of 30 ground-truth answers were wrong at first. For four of six agents, the notice runs were collected 3–4 weeks later, some on a different server.
The main idea (telling the agent that data is missing helps) is also somewhat expected, so the contribution is mostly the careful measurement.
Questions for authors
- Does the effect hold with larger data and with top-k search results?
- Can you add human labels for a sample of runs, to check the judge?
- Can you re-run the notice condition for all six payload agents in the same time window as their other conditions?
Thank you. Each question now has new evidence: larger data and top-k (§4.7), human labels (App. M), and a same-window re-run (App. W.3).
Q1: larger data and top-k. Top-10 search with no total and a 4,000-character cut, on 14–222 records with 29–82% withheld (general comment, items 1–2). The silent limit leaves no agent correct; the page or offset parameter restores 67–89% correct for the Claude agents. The effect holds for Haiku at every share and for Sonnet 5 when half or less is withheld (App. W.2).
Q2: human labels. One author labelled 280 runs blind to agent, condition and grader: four-way agreement 94.3% with Opus 4.8 (κ=0.91) and 96.1% with GPT-6.1 (κ=0.94). Of the 24 disputed partial answers the LLM-free rule accepts, the annotator rejects 21. One annotator and an author, so not independent (general comment, item 4).
Q3: same-window re-run of the notice. Done for the four agents whose notice arm came later, now in one window on one service. GPT-4.1-mini and Gemini ran all four payload conditions, the notice included, on 10 September; their fault-free runs are the main grid's from 7 September.
Other concerns.