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

The readOnlyHint annotation already establishes the tool as non-mutating. The description adds that the tool returns both the converted amount and the exchange rate, which is useful context, but it does not disclose any potential caveats such as rate sourcing, latency, or supported currency limitations. With annotations covering the safety profile, this is adequate but not exceptional.

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, compact sentence that efficiently conveys the tool's purpose and output. It avoids unnecessary words and front-loads the key information, making it easy for an agent to parse.

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 straightforward converter with a simple parameter set and an output schema, the description covers the essential aspects: what it converts, what it returns, and the types of assets involved. It lacks discussion of edge cases or rate specifics, but these are not critical for a basic read-only tool. The description is complete enough to guide invocation.

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?

The input schema provides descriptions for all three parameters (amount, from_currency, to_currency) with examples and constraints, achieving 100% coverage. The tool description does not add further semantic detail beyond what the schema offers, so the baseline 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?

The description clearly states that the tool converts between fiat currencies and crypto assets, using the specific verb 'convert' and naming the resource ('currency' and 'assets'). It also specifies the return values (converted amount and exchange rate), which distinguishes it from price-lookup tools like get_token_price.

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 the tool is for currency conversion but does not explicitly mention when to prefer it over sibling tools such as get_token_price or get_dex_quote. No exclusions or alternative usage scenarios are provided, leaving the agent to infer the appropriate context from the tool's name and description.

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