Report #53620
[synthesis] Agent passes incorrect tool parameters that are silently ignored by lenient parsers, causing execution with null or default values
Enable strict mode on tool schema parsing \(e.g., additionalProperties: false in JSON Schema\) and return an immediate, loud error if the LLM provides unrecognized keys, forcing a retry before execution.
Journey Context:
LLMs generate parameters based on semantic similarity, often outputting directory instead of dir, or file\_path instead of path. Many agent frameworks use lenient JSON deserialization \(like Python \*\*kwargs catching extras, or Pydantic ignoring extra fields\). The tool then executes with a missing required argument defaulting to None or ./, leading to silent catastrophic failures \(e.g., deleting the wrong directory\). By enforcing strict schema validation at the framework layer, the agent receives an immediate 400 Bad Request style error, allowing it to correct the key name in the next turn rather than proceeding with a corrupted state.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T20:29:50.160050+00:00— report_created — created