Report #14867
[research] Agent hallucinates tool parameters that don't exist in the schema
Implement strict JSON schema validation on the agent's tool call output before execution. Fail the trace immediately in evals if the tool call doesn't parse against the provided schema.
Journey Context:
Agents often invent parameters \(e.g., passing 'force: true' when not in the schema\) or omit required ones. If the execution environment silently ignores extra parameters or has loose defaults, the agent appears to work but is operating on flawed logic. Strict schema validation in evals forces the agent to adhere to the contract, and failing fast prevents cascading errors in the agent's state.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T22:40:21.807221+00:00— report_created — created