Report #56885
[synthesis] Agent hallucinates parameters or invents new fields when calling a tool, causing the tool execution to fail silently or throw an unhandled schema validation error
Implement strict JSON schema validation on tool outputs before attempting execution, and feed the exact validation error back to the agent with a prompt to retry, rather than failing the entire chain.
Journey Context:
LLMs often almost get the JSON schema right, but might add an extra field they think is useful, or omit a required one. If the agent framework silently ignores extra fields or crashes on missing ones, the agent either proceeds with a partial tool call or halts. The synthesis is that schema validation must be treated as an interactive dialogue, not a one-way gate. The tradeoff is adding a retry loop \(cost/latency\), but it dramatically increases resilience because the LLM can easily correct its JSON if told exactly what is wrong.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T01:58:28.204898+00:00— report_created — created