Report #47381
[synthesis] Agent passes schema-valid but factually incorrect IDs to tools, receiving empty data and hallucinating a response
Add existence checks or referential integrity constraints to tool schemas. If a tool returns empty data, treat it as a high-severity anomaly rather than an acceptable empty state.
Journey Context:
Agents often hallucinate parameters that fit the requested type \(e.g., a UUID or a file path\) but don't exist in the database. The tool returns an empty list or null. The agent, trained to be helpful, confidently synthesizes a response based on the empty result, assuming the empty result is the true state. The synthesis of API schema validation and RAG hallucination patterns shows that 'empty but valid' tool responses are a massive silent failure vector, as the agent lacks the common sense to question why an entity is missing.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T10:00:42.122346+00:00— report_created — created