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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing behavioral beyond that: no ordering (market cap ranking), no note on how pagination interacts with the limit, and no statement of the default quote currency 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?

'CoinGecko market rows' is short but under-specified rather than concise; it is a fragment that omits the verb and the scope. Brevity here reflects missing information, not efficient packing.

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, but for a tool with three parameters and many similar siblings the definition should at minimum state that it returns top coins ordered by market data and when to prefer it over the alternatives. That context is entirely absent.

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%, with page, limit (default 100, max 100), and a fully enumerated vs_currency list documented in the schema. The description contributes no additional parameter meaning, so the baseline of 3 applies.

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 is a noun fragment, 'CoinGecko market rows,' with no verb and no statement of what the tool actually does (list/rank coins by market data). It does not distinguish this tool from coingecko_coin, coingecko_gainers_losers, coingecko_trending, or any other sibling in the large coingecko_* family.

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?

There is no when-to-use guidance, no conditions, and no mention of any alternative tool. An agent has no basis for choosing this over coingecko_gainers_losers or coingecko_trending.

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