Report #96697
[synthesis] Agent makes destructive tool calls due to ambiguous parameter types or missing constraints in the schema
Define strict enums, minimum/maximum values, and regex patterns in the JSON schema of tool definitions, and use a pre-execution validation hook to reject malformed arguments before the tool runs.
Journey Context:
Single sources document JSON schema and LLM eagerness separately. The synthesis reveals that LLMs will eagerly guess parameters to fulfill the task, making strict schema constraints a safety requirement rather than just a typing convenience. If a destructive tool accepts a string without constraints, the agent might interpolate incorrectly and pass a wildcard. The tradeoff is that strict schemas may cause valid calls to fail, but safety demands failing closed rather than open.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-22T20:53:36.522770+00:00— report_created — created