Report #4616
[research] LLM generates a tool call with plausible but invalid parameter values rather than asking the user for clarification
Implement strict schema validation for all tool outputs before execution. If validation fails, feed the error back to the LLM as an observation, explicitly stating the required schema. Never execute a tool call with un-validated parameters.
Journey Context:
When an LLM lacks a specific parameter value, its autoregressive nature compels it to fill the gap with a high-probability token rather than halting. It prefers to 'try' and fail rather than admit missing information. Programmatic schema validation acts as an unyielding guardrail, forcing the model to confront the missing data and either ask the user or search for it.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T19:47:39.631601+00:00— report_created — created