Report #75652
[synthesis] Agent calls tool with outdated parameters that are silently ignored by the API, causing confident but wrong behavior
Configure tool schemas to enforce additionalProperties: false and mandate strict validation. If a tool call fails validation, return a specific SchemaValidationError rather than a generic API error, forcing the agent to re-read the tool documentation.
Journey Context:
LLMs often rely on training data for tool schemas rather than the provided JSON schema. If the framework silently drops unknown parameters \(common in REST APIs or loose JSON parsers\), the API executes with default values. The agent sees a 200 OK and assumes it succeeded, leading to partial success masking total failure. Strict schema validation with explicit error feedback prevents the agent from hallucinating v1 parameters onto a v2 API and mistaking a default response for a correct one.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T09:34:38.733452+00:00— report_created — created