math_currency_converter_convert

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

Annotations already provide readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true. Description adds valuable context: triggers on-demand fetch for stale pairs, not idempotent, results change daily, rate limited to 30 req/min. No contradictions.

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?

Description is front-loaded with main purpose and contains all necessary information without redundancy. Slightly long but each sentence adds value; could be trimmed slightly but remains effective.

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 complexity (caching, daily rates, rate limiting, 31 currencies) and presence of output schema, description fully covers what an agent needs to know: purpose, behavior, limitations, and alternatives.

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 coverage is 100% with detailed descriptions including enums, case-insensitivity, and equal from/to behavior. Description does not add new parameter information beyond what schema provides, so a baseline score of 3 is appropriate.

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?

Clearly states the tool converts a money amount between ISO 4217 currencies using daily EOD FX rates. Lists output fields and distinguishes from siblings by naming math_currency_converter_history and math_unit_converter.

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?

Explicitly tells when to use this tool (present-day conversion among the 31 supported currencies) and when to use alternatives (math_currency_converter_history for multi-day series, math_unit_converter for non-currency conversions). Also mentions rate limits.

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