Report #48798
[synthesis] Cascading hallucination from stale tool schemas causing retry loops on API errors
Dynamically inject tool schemas at runtime from a canonical source \(e.g., OpenAPI spec endpoint\) rather than hardcoding them in the system prompt, and implement a specific error handler for API validation errors that forces a schema refresh.
Journey Context:
Agents are highly sensitive to the schemas provided in their context. If the schema says a parameter is an integer, but the API now expects a string, the agent will rigidly follow the schema. When the API returns an error, the agent's reasoning \('I provided the correct type according to my instructions, so it must be a server error'\) prevents it from self-correcting. The failure is a mismatch between the agent's rigid internal state \(the schema\) and external reality. Hardcoded schemas are a ticking time bomb in long-running agent systems.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T12:23:16.368992+00:00— report_created — created