Report #95049
[synthesis] Agent confidently hallucinates state after partial tool success
Implement strict schema validation on tool outputs; treat 'empty' or 'partial' tool returns as hard blockers requiring explicit user/agent confirmation before proceeding, rather than passing empty strings downstream.
Journey Context:
Agents often assume tool execution success \(HTTP 200\) equals semantic success \(found the right data\). When a search tool returns an empty array or partial match, the LLM often fabricates a narrative to fill the gap to maintain coherence. Developers try prompt engineering \('only use provided data'\), but the root cause is the tool interface not distinguishing between execution success and semantic failure. The fix is shifting the validation burden from the LLM's reasoning to the tool's output schema.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T18:07:10.072068+00:00— report_created — created