Report #99220
[agent\_craft] Tool arguments and results are free text, forcing the agent to parse before acting
Define tool inputs and outputs with strict schemas \(JSON Schema, Pydantic, or XML schema\). Require the model to emit structured tool calls, and return tool results as JSON or XML with fixed fields. Validate every argument before execution and reject calls that violate the schema.
Journey Context:
Free-text interfaces create parsing fragility: the model hallucinates argument formats, tools return blobs the model must re-read, and small syntax errors cascade. Structured I/O turns tool use into a typed API call. It also enables validation, retry on schema violation, and clearer error reporting. The function-calling APIs from major providers are built around this principle because it reliably outperforms asking the model to produce raw commands.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-29T04:46:09.195299+00:00— report_created — created