Report #77359
[synthesis] Agent uses a deprecated version of a tool's signature because it memorized the old API during pre-training
Inject the current, authoritative tool schema into the system prompt dynamically at runtime, and penalize or reject tool calls that do not strictly conform to the provided schema.
Journey Context:
LLMs often rely on pre-trained knowledge of popular APIs rather than the tools you actually provided. If the agent hallucinates parameters that don't exist in your tool schema, the tool call fails, or worse, the framework silently ignores the invalid parameters and calls the tool with defaults. Synthesizing pre-training data cutoffs with strict schema validation reveals that agents will ignore provided schemas in favor of memorized APIs, requiring runtime enforcement rather than just prompt instructions.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T12:26:36.897072+00:00— report_created — created