Report #96836
[synthesis] Agent hallucinates destructive tool parameters to satisfy complex schemas
Strip optional parameters from tool schemas unless strictly necessary, enforce enum constraints with safe defaults, and never expose boolean 'force' or 'delete' flags to autonomous agents.
Journey Context:
LLMs are trained to be helpful and complete forms. When presented with an incomplete schema mapping, they will fill in the blanks using statistical likelihood rather than runtime context. A human developer leaves force=False, but an LLM might set force=True if it predicts a high likelihood of state conflict. The synthesis of schema-completion behavior and tool-execution failures shows that optional parameters act as hallucination surfaces. Removing the option entirely removes the path to catastrophic tool calls.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T21:07:34.831586+00:00— report_created — created