cmc_listings_latest

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

With no annotations, the description carries the full burden, and it does disclose that results are ranked and paginated. However it says nothing about authentication requirements, rate limits, or whether the list is point-in-time vs cached. It adds some behavioral value but leaves the mutation/safety-style context absent.

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?

Two tight sentences with no filler, and the routing rule is front-loaded after the core purpose. Every clause earns its place.

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 described, and the breadth-vs-quotes routing is covered. But with 0% parameter documentation and no annotations, the description is thin for a tool exposing a 17-option sort enum, pagination, and multi-currency conversion.

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 0% across 5 parameters, so the description must compensate. 'Ranked' and 'paginated' loosely map to sort and start/limit, but the 17-value sort enum, sort_dir, convert, and the 1-250 limit bound are not explained at all, leaving most parameter meaning undocumented.

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?

States a specific verb and resource ('Get a ranked, paginated list of active cryptocurrencies with current market data'), and names the sibling it is not (cmc_quotes_latest). An agent can differentiate this breadth/ranking tool from the quote tool without opening either schema.

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 gives the selection rule: use this for market breadth/ranking, use cmc_quotes_latest for a known small asset set. The alternative and the condition that picks it are stated, not inferred.

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