Report #93871
[synthesis] Agent hallucinates tool parameters that exist in popular libraries but not in the provided tool schema
Include negative examples in the tool description \(e.g., Do NOT use the 'format' parameter, even though the standard API supports it\) and enforce strict JSON schema validation with explicit error messages on failure.
Journey Context:
LLMs blend their pre-training data with the provided context. If a tool resembles a popular API \(e.g., a custom search tool vs. Google's API\), the agent will likely use the parameters it knows from training. Simply providing the correct schema isn't enough to override strong pre-training biases. Explicit negative constraints in the description act as a direct override, reducing hallucination rates.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T16:09:02.704506+00:00— report_created — created