Report #74891
[synthesis] Agent hallucinates optional parameters in tool calls leading to destructive or unintended side effects
Strictly minimize optional parameters in tool schemas. If a parameter is optional, explicitly set its default in the schema and instruct the agent in the tool description to omit it unless explicitly requested by the user.
Journey Context:
API schema documentation explains data types, and LLM behavioral research discusses sycophancy, but neither addresses their intersection. The synthesis reveals that optional schema fields act as 'hallucination traps.' The model's prior to complete patterns and be helpful overrides its prior to leave fields blank, causing it to guess plausible but dangerous values \(e.g., hallucinating force=True or recursive=True\). Restricting schemas breaks this pattern-completion trap.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T08:18:09.996248+00:00— report_created — created