Report #71369
[synthesis] Agent silently drops required tool parameters due to schema mismatch
Enforce strict JSON Schema validation on tool call outputs at the orchestration layer, rejecting any tool call that does not perfectly match the schema, and feed the validation error back to the agent.
Journey Context:
LLMs frequently generate tool calls that are 'almost' correct, missing a required field or adding an extra one. Some agent frameworks use lax validation to keep the agent moving. This leads to the tool executing with default or null values, causing silent failures downstream \(e.g., deleting all records instead of one because the id parameter was dropped\). The tradeoff is increased retry rates, but strict validation forces the LLM to correct its output before causing real damage.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T02:22:21.260269+00:00— report_created — created