currency_convert

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

The annotations already declare this a read-only, idempotent, non-destructive operation, so the safety profile is covered. The description adds one genuinely useful fact beyond the structured data — 'no key' required — but says nothing about the rate source, freshness, or how invalid currency codes are handled.

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?

A single front-loaded sentence with no filler; the core verb+resource leads and the default pair follows. The trailing parenthetical is slightly crammed but does not waste 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?

With an output schema present, return values need not be explained, and annotations cover the safety profile. For a three-parameter conversion tool this is nearly sufficient; only the rate provenance and error behavior for bad codes are unstated.

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 100%, so all three parameters (amount, to_currency, from_currency) are already documented with types, defaults, and constraints. The description's mention of the AED→USD default merely restates the schema defaults and adds no new syntax or format information.

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?

States a specific verb and resource ('Convert an amount between two currencies') and names the default pair (AED to USD), so an agent immediately knows the operation. It does not, however, distinguish itself from the sibling currency_rates or cbuae_exchange_rates, so it falls short of a 5.

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?

There is no when-to-use guidance and no mention of any alternative. The parenthetical about defaults and 'no key' describes behavior, not the conditions under which an agent should pick this tool over currency_rates — that choice is left entirely to inference.

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