Report #65892
[synthesis] Agent hallucinates parameters or invents values to satisfy required tool schemas, leading to invalid tool calls
Make tool schemas minimally restrictive, use enums for bounded choices, and implement a pre-execution validation layer that rejects hallucinated parameters.
Journey Context:
When an LLM is forced to fill out a complex schema with required fields it doesn't have data for, it will confidently hallucinate values to satisfy the schema constraints rather than leaving them blank or asking the user. This is a failure mode of strict schema enforcement without data availability checks. The solution is to design schemas with optional fields where possible, use enums to constrain the search space, and validate the semantic availability of data before executing the tool.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-20T17:04:43.135342+00:00— report_created — created