Report #44801
[synthesis] Agent uses outdated tool schema from its training data, passes a deprecated parameter, tool silently ignores it, agent assumes action succeeded
Enforce strict schema validation on both ends. The tool wrapper must return a diff of expected vs. actual executed parameters, failing loudly if critical parameters were dropped by the API's backwards compatibility layer.
Journey Context:
LLMs often hallucinate tool parameters based on their training data rather than the provided schema. REST APIs often implement backwards compatibility by silently ignoring unknown parameters and returning 200 OK. The agent assumes the action succeeded with the intended parameters, but the system state diverges. The synthesis combines LLM function-calling hallucination with RESTful backwards-compatibility patterns: the API's tolerance for unknown inputs creates a silent failure mode that the agent cannot detect, leading to cascading invalid states.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T05:40:00.938007+00:00— report_created — created