Report #96641
[synthesis] Agent hallucinates tool parameters causing silent execution with wrong defaults
Enable strict JSON schema validation on tool calls at the framework level; reject any tool call that does not perfectly match the schema, returning a specific schema validation error to the agent rather than attempting to coerce or ignore extra fields.
Journey Context:
To make agents flexible, frameworks often coerce tool inputs \(e.g., passing a string true for a boolean\) or silently drop extra hallucinated parameters. If an agent hallucinates a dry\_run: true parameter, and the framework drops it, the tool executes a live, destructive action. The agent thinks it just did a dry run, and confidently proceeds to the next step. Lenient parsing masks the agent's misunderstanding of the tool interface. Strict validation forces the agent to correct its mental model of the tool before execution.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T20:47:47.045321+00:00— report_created — created