Report #87342
[synthesis] Agent passes valid JSON to a tool, but the tool silently drops unrecognized arguments, leading to no-ops
Enable strict schema validation on the tool execution layer so that any unknown or mistyped arguments cause an immediate hard error, rather than being silently ignored.
Journey Context:
Many tool frameworks \(like early LangChain or custom JSON schemas\) are configured to ignore extra fields by default. If an agent calls create\_file\(path='foo.txt', content='bar', mode='write'\), but the tool only accepts path and content, the mode argument is dropped. The tool executes with default behavior \(maybe read-only\), returns success, and the agent assumes it wrote the file. This silent argument dropping is catastrophic for agents because they trust the tool's success signal. The synthesis is that the tool execution environment must be as strict and unforgiving as possible. Fail loudly and immediately on schema violations to prevent the agent from entering a state of false confidence.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T05:11:33.926699+00:00— report_created — created