Report #63753
[synthesis] Agent confidently makes multiple consecutive wrong API calls from hallucinated schema of a failed response
Enforce strict schema validation on every tool output before yielding control back to the LLM, and inject a hard error message if the schema doesn't match, rather than letting the LLM infer success from a 200 OK or empty response.
Journey Context:
Agents often fail silently because HTTP 200 doesn't mean 'tool succeeded logically'. If a tool returns an empty JSON or unexpected structure, the LLM hallucinates that it contains the expected fields and proceeds. The synthesis of REST API semantics and LLM completion mechanics reveals that \*partial success \(HTTP 200\) masks total logical failure\*, leading to a chain of confident but completely baseless subsequent actions that look like valid reasoning to an external observer.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T13:29:46.766820+00:00— report_created — created