math_currency_converter_convert

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full disclosure burden. It mentions 'daily end-of-day FX rates' indicating data freshness, but lacks details on input validation, output format, rate limits, or side effects. The mention of 'JSON API endpoint' is ambiguous regarding tool behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is relatively short but includes irrelevant details such as 'Interactive history chart, percentage change overlay, inverse rate' which describe webpage features rather than the tool's core function. This reduces conciseness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (3 parameters, no output schema, no annotations), the description is insufficient. It fails to explain how to specify currencies, what the response contains, or how to handle errors. It relies on describe_tool to compensate, making it incomplete for standalone use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, and the description does not explain the parameters (from, to, amount). It does not specify expected formats (e.g., currency codes) or provide examples, leaving the agent without guidance on valid inputs.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Currency Converter' and 'Convert between 31 world currencies using daily end-of-day FX rates', specifying the verb (convert) and resource (currencies). It distinguishes from sibling tools like math_currency_converter_history by focusing on current conversion, not historical data.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for current currency conversion but does not explicitly state when to use this tool versus alternatives like math_currency_converter_history. The suggestion to use describe_tool for full guidance is indirect.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.