crypto_top_coins

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds the useful fact that results are ranked by market cap and sourced from CoinGecko, but it does not mention pagination behavior, default page size, or rate limits.

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 a single efficient sentence with the core purpose front-loaded. It is appropriately concise, though its brevity contributes to gaps elsewhere rather than being a structural flaw.

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 tool with three undocumented parameters and no output schema, the description is too thin. It does not explain parameter meanings, return shape, pagination, or how results differ from sibling crypto listing tools.

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% and all three parameters (page, per_page, vs_currency) are undocumented in the schema. The description does not explain any of them, including what vs_currency accepts or default pagination behavior, so it does not compensate for the coverage 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 clear verb and resource: 'Get top cryptocurrencies by market cap', plus the data source CoinGecko. It is understandable in isolation, but it does not distinguish this tool from numerous sibling crypto listing tools such as cmc_listings, coinlore_tickers, coincap_assets, or coinpaprika_ticker.

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 guidance on when to use this tool versus alternatives. With many crypto tools in the sibling list (crypto_trending, crypto_search, cmc_listings, etc.), the agent is left to infer which one provides top-by-market-cap data.

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