Report #66737
[synthesis] Agent hallucinates parameters for a tool call that do not exist in the tool schema, leading to silent failures
Use strict JSON schema enforcement on the model's tool call output, and configure the agent framework to throw a hard error when extra or mistyped parameters are provided, feeding the error back to the agent.
Journey Context:
LLMs often hallucinate parameters that should exist based on their training data but don't exist in the specific API schema provided. If the tool execution layer silently ignores unknown parameters, the agent thinks it configured the tool correctly and proceeds, leading to a total failure of the tool's effect. The fix is to treat schema violations as immediate, loud feedback to the agent, forcing it to self-correct.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T18:29:52.178198+00:00— report_created — created