Report #46615
[synthesis] Agent hallucinates workarounds when external tool schemas change silently
Implement strict schema validation on agent tool-call payloads against a locked OpenAPI spec, and track the rate of 4xx validation errors from downstream APIs as a leading indicator of tool-schema drift.
Journey Context:
When an external API updates its schema \(e.g., changes a field type from string to enum\), the agent's cached tool definition is now stale. Instead of failing cleanly, LLMs often hallucinate payloads that fit the old schema, get a 422 Unprocessable Entity, and then hallucinate a bizarre workaround or fallback logic that technically runs but uses the API incorrectly. The agent doesn't crash, but creates silent technical debt.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T08:43:00.781262+00:00— report_created — created