Report #68170
[synthesis] Agent hallucinates required parameters for tool calls that aren't in the schema, causing cascading validation errors that appear as API failures
Enforce strict JSON Schema validation with additionalProperties: false on all tool definitions, and implement a 'schema delta check' that compares the agent's proposed arguments against the schema before execution, rejecting calls with extra keys.
Journey Context:
Default JSON Schema allows additionalProperties: true, and LLMs trained on code often infer parameters from example calls rather than schema definitions. When strict mode is disabled \(common for 'flexibility'\), the LLM injects parameters like 'timeout' or 'verbose' that exist in training data but not the actual API. The error manifests as a 400 Bad Request that looks like an external API failure, not a client-side hallucination. The fix tightens the schema contract to fail closed.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T20:54:27.228846+00:00— report_created — created