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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and openWorld, so the safety profile is covered. The description adds genuine behavioral context beyond that: it discloses pagination via the page parameter and the auth requirement (own API key), which an agent needs to know before calling.

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?

A single tight sentence with the ranking and scope front-loaded, followed by pagination and auth notes. No wasted words; each clause carries distinct information.

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 covers scope, pagination, and auth. The only shortfall is the undocumented limit parameter, which leaves the agent without guidance on controlling the result count.

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 only 25% (only _apiKey is documented in the schema). The description compensates for tsym (quote symbol) and page (pagination), adding meaning for two of four parameters, but limit is left unexplained in both the description and the schema, leaving a real gap.

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 gives a specific verb (Return), a clear resource (top cryptocurrencies), and the ranking metric (24h total volume), which implicitly sets it apart from the sibling top_market_cap. It is unambiguous about what the tool returns, though it does not name an alternative outright.

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 states the API-key prerequisite and mentions pagination, which is useful context for invoking it, but gives no explicit when-to-use vs. when-not guidance and does not route the agent to sibling tools like top_market_cap for cap-based rankings. Usage is implied rather than stated.

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