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

With no annotations, the description carries the burden and does so well: it discloses payload size (~1 KB per asset with market), the default of 20 and max of 250, that unpriced-in-quote items are silently skipped, and it routes edge cases to the ratehub://docs/behavior resource. Rate-limit and auth behavior are only pointed at rather than stated, keeping it below a 5.

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?

Front-loaded with the core purpose, then size, defaults, and edge cases in a logical order with no filler sentences. It is slightly cramped and mildly redundant, restating the market block contents after already naming it.

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?

An output schema exists, so return values need not be explained, and the description instead supplies the operational facts an agent needs: defaults, caps, compaction flag, skipped-item behavior, and a pointer to deeper behavioral docs. Complete for a three-parameter listing tool, with only rate limits/auth left implicit.

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%, so the baseline is 3, but the description genuinely adds meaning: include_market is tied to the ~1 KB size figure and 'both copies of the result', and the default limit behavior is restated in context. That is more than a paraphrase of the schema, though it doesn't explain the `vs` quote-currency mechanics in any depth.

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+resource ('Top crypto assets by market rank') and adds the underlying endpoint GET /v1/top, so the operation is unambiguous. It does not, however, differentiate itself from the sibling search_assets or get_series, leaving the agent to infer which listing path applies.

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?

Usage is implied rather than stated: 'pass include_market=false for a compact list' and the default/max limit tell the agent how to tune a call, but there is no when-to-use-this-vs-search_assets guidance and no explicit exclusions. Adequate but with a clear gap around alternatives.

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