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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the $0.001 USDC per-call cost and names the returned fields, but it omits rate limits, data freshness, authentication requirements, and error behavior for unknown assets.

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 three short sentences and front-loads the core purpose. The second sentence largely duplicates the schema, but the cost sentence earns its place and nothing is bloated.

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 one-parameter read tool with no output schema, the description lists the main returned fields and the accepted query forms, which is enough to call it correctly. The remaining gap is sibling differentiation rather than missing parameter or return-value context.

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 the single query parameter is already well documented with examples. The description repeats that name, symbol, and CoinGecko ID are accepted but adds little beyond the schema's own wording.

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 a specific verb and resource: get current price, market cap, volume, and 24h/7d change for any cryptocurrency. It also specifies search by name, symbol, or CoinGecko ID. It is clear, but it does not explicitly distinguish crypto_price from the sibling 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?

It does not say when to use this tool instead of token_price, dex_search, or pair_data, and it provides no exclusions or prerequisites. The cost note is useful context, but it is not usage guidance.

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