currency_convert

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

With no annotations provided, the description carries the full burden. It only mentions 'no key' (no authentication) but fails to disclose whether rates are live, cached, or any rate limits, which is critical for a conversion tool.

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 a single, efficient sentence with no redundancy. It front-loads the action and adds key context (defaults, no key) without wasting words.

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?

For a simple conversion tool with an output schema, the description covers the basics. However, it omits behavioral details like whether the conversion uses current market rates or is static, which matters for financial decisions.

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%, so the schema already documents all parameters. The description adds the defaults ('AED', 'USD') and 'no key' context, but these are already implied or partially in the schema. Baseline score 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?

The description states 'Convert an amount between two currencies' with specific defaults (AED to USD), which clearly identifies the tool's function. It does not explicitly distinguish from the sibling 'currency_rates' tool, but the defaults and 'no key' hint provide differentiation.

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 'no key' as a prerequisite, but lacks guidance on when to use this tool versus alternatives like 'currency_rates'. No explicit context for preferred usage or exclusions is provided.

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