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

Discloses cost ($0.02 per call via x402) and output nature (written summary), adding value beyond annotations which already indicate read-only, idempotent behavior.

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?

Single concise sentence with additional cost note. Front-loaded with key details, though lacks bullet points or structured formatting.

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 output schema present, the description sufficiently covers input, output type, use case, and cost. No missing critical information for tool selection.

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 fully describes the parameter as a CoinGecko asset id with examples. Description adds 'for one asset' but this is already implicit. Minimal incremental value for the parameter.

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 specifies 'Enriched crypto market report for one asset' and lists concrete data fields (rank, price changes, ATH context, signals, summary), clearly differentiating from sibling get_price_coin.

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?

Explicitly states 'For agents needing market context, not just a price' which indicates when to use this tool over alternatives, though it could name the sibling explicitly.

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