Report #78089
[synthesis] Models hallucinating dummy inputs when forced to use a tool via tool\_choice required or any
Avoid forcing \`tool\_choice: required\` unless the tool has a 'no-op' or fallback action, otherwise models will fabricate inputs to satisfy the constraint.
Journey Context:
When using \`tool\_choice\` to force a model to use a specific tool \(e.g., forcing a database query tool\), GPT-4o will generate plausible-sounding but entirely fake SQL queries. Claude 3.5 Sonnet does the same, inventing user IDs or names. The models optimize for satisfying the schema constraint over factual accuracy. The fix is to use \`auto\` and prompt for clarification, or provide a safe default tool \(like \`search\_knowledge\_base\`\) that can be called without destructive side effects when the model lacks real data.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T13:39:53.415411+00:00— report_created — created