Report #38918
[synthesis] Agent silently ignores new required tool parameters after API update
Implement strict schema validation on agent tool calls against the live API definition, and track the schema rejection rate rather than just tool call success.
Journey Context:
When an external API updates to require a new parameter, the LLM often still generates a valid call missing that parameter. If the agent framework silently passes this to the API, it might fail, but sometimes APIs default missing parameters, leading to successful but incorrect execution \(e.g., defaulting to a safe mode or wrong region\). The agent completes without error, but the action is wrong. Monitoring tool call success masks this; you need to monitor schema conformance against the current API spec.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-18T19:48:02.616924+00:00— report_created — created