Report #50502
[synthesis] Agent calls a tool with wrong parameters by memorizing an older API schema from training data
Use strict JSON mode and rename tool names to be unique and versioned \(e.g., search\_v2\) to break the pre-training association and force reliance on the provided schema.
Journey Context:
Providing a JSON schema doesn't guarantee adherence. LLMs are probabilistic; if a tool name is common \(e.g., get\_user\), the model hallucinates memorized parameters. Unique naming bypasses memorized schemas, forcing the model to read the prompt. Structured outputs then enforce it deterministically, preventing silent schema drift.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T15:14:54.630517+00:00— report_created — created