Database
Who Verifies the Tools? How Warped Formatters Mislead Agents and Their Verifiers
arXiv cs.SE0 views
arXiv:2610.32110v1 Announce Type: cross Abstract: Agents and verifiers often rely on the text a tool prints, and that text can misrepresent what the tool actually did, even when the tool's computation is correct. We saw this happen in a production RAG research system used by the Pilsudski Institute in New York, where tool output formatters misled an agent into giving wrong or incomplete information to users. Each tool did its job correctly, but its output omitted search limits, result caps, or identifier namespaces. We also recreated an unlabeled estimate caught in code review before release. We studied whether these formatters misled agents and verifiers and how much the repaired wording helps. We fed tool results to agents using two formatter versions: one with the key omissions and one with all missing details clearly stated. That difference alone changed what the agents claimed and what the verifiers accepted. Unsupported agent claims dropped substantially for three of the four failure types. In one test, verifiers went from accepting incorrect answers 90 out of 90 times to rejecting them 90 out of 90 times. A control showed the verifiers could catch the errors once they were given the missing facts and asked to judge correctness. We include the audit prompt we used with Codex and Claude Code in an exploratory demonstration, written with prior knowledge of our own system's defects. When pointed at an old version of our own system, it rediscovered the defects that were still live and surfaced twelve more we had not catalogued. When pointed at OpenClaw and Hermes, two of the best-known open-source agentic systems, it found warped formatters in both. We opened PRs to fix both, and the OpenClaw fix has already been merged. Practitioners can run the same prompt on their own systems today.
Source:https://arxiv.org/abs/2610.32110PreviousPermission to Retry: A Study of Authorization and Recovery in AI Agent WorkflowsNextSearch-Based Testing of Modality Sensitivity in Vision Language Models
Related posts
Postgres LISTEN/NOTIFY vs Redis Pub/Sub: Latency, Write Cost and Failure Cases, Tested
0dev.to Node
LlamaIndex Workflows vs LangGraph: Event-Driven Architecture and Async State Overhead Showdown
0dev.to Programming

Rider and Databases: Lesser-Known IDE Features That Save Time
0dev.to Database
KivaDB v2: What's Coming and How You Can Contribute
0dev.to Database
Your LLM cost log says $0.00. The invoice says $1,320.
0dev.to Database
SQLite in Production: A Practical Setup with Litestream Backups
0dev.to Database