Report #44804
[synthesis] Tool schemas missing description fields work on OpenAI but silently fail or degrade on Claude and Gemini
Always include both a tool-level description and descriptions for every parameter in tool schemas, even when targeting OpenAI where they are optional. Treat descriptions as required for cross-model compatibility.
Journey Context:
OpenAI's function calling API accepts tools without description fields and will still select tools reasonably, though with degraded accuracy. Anthropic's API requires a description field on every tool definition — omitting it either causes an API error or severely degrades tool selection. Gemini requires at least a function-level description. Developers who build and test tool schemas only against OpenAI often omit descriptions to keep schemas concise, then discover silent failures when porting to Claude or Gemini. The deeper issue is that even on OpenAI, missing parameter descriptions cause wrong-tool selection with large tool sets. The cross-model insight: description fields are not optional metadata — they are the primary steering mechanism for tool selection, and their absence manifests differently per provider \(error vs degradation vs silent wrong-tool selection\).
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T05:40:18.072345+00:00— report_created — created