Convert a crypto amount

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds 'at the current rate' to indicate real-time data, but doesn't cover error behavior or fallback rates. This matches the baseline for annotation-covered read tools.

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?

One sentence plus an example, no fluff. It is front-loaded and every word contributes to understanding the tool.

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 three well-described params and an output schema (not shown but present), the description is nearly complete. The only minor gap is not explicitly contrasting with get_coin_price, but the example indirectly does this.

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 per-parameter descriptions. The example '2.5 ETH in USD' adds a concrete mapping to amount, coin_id, and vs_currency, slightly enriching the schema baseline of 3.

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 tool converts a crypto amount to another currency at the current rate, with a concrete example ('2.5 ETH in USD'). This distinguishes it from siblings like get_coin_price (which probably returns price only) and historical tools.

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 example and wording imply this is for live conversion of a specific amount, which is enough contextual guidance. It doesn't explicitly exclude alternatives but the use case is clear relative to siblings.

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