tool_convert_currency

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

With no annotations, the description carries full burden. It states 'live rates' and 'no auth required', suggesting a read-only, real-time operation. However, it does not disclose specific constraints such as supported currencies, rate freshness, or potential side effects.

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 extremely concise: two clear sentences followed by an Args list. Every sentence adds value, with no wasted words. The key information is front-loaded.

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 simplicity (3 params, no output schema), the description is minimally adequate. It explains the purpose, auth requirement, and parameter examples, but omits return value details and potential error scenarios.

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 0%, so description must compensate. The Args section lists parameters with example values (e.g., 'USD', 'EUR'), adding meaning beyond schema titles. However, it lacks detail on amount type or currency format, and does not explain all parameter semantics thoroughly.

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 the verb 'convert' and resource 'currencies', and highlights live rates. It distinguishes from sibling tool_get_exchange_rates, which probably only provides rates, while this tool actually converts amounts.

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 notes that no auth is required, but does not explicitly guide when to use this tool over alternatives like tool_get_exchange_rates. The usage context is implied but not reinforced with exclusions.

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