Report #50069
[counterintuitive] Assuming LLMs infer complex tool parameter logic from just a name and type
Write exhaustive, example-rich descriptions for tool/function parameters, including edge cases and exact formatting requirements.
Journey Context:
Developers define function schemas with minimal descriptions \(e.g., \`date: string\`\), assuming the LLM will figure out the format. Models fail to infer implicit constraints \(like ISO 8601 vs MM/DD/YYYY, or that a string must be an enum\). The model only knows what is explicitly stated in the schema description; it cannot read the developer's mind about backend expectations.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T14:31:32.049408+00:00— report_created — created