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

With no annotations, the description carries full burden. It discloses the limit clamping (1–100, default 10) and defaults for lang and provider, but does not mention any behavioral traits like read-only nature, rate limits, authentication requirements, or side effects. The disclosure is adequate but incomplete.

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 concise sentences: the first states the core purpose and fields, the second answers the user query and clarifies parameter behavior. No redundant words; every sentence adds value.

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?

Given the presence of an output schema (so return values are covered), the description explains all three optional parameters and the clamping behavior. It lacks details on error handling or provider limitations, but for a straightforward listing tool, the information is sufficient.

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?

The input schema has 0% description coverage, so the description must compensate. It adds meaning for limit (clamped range) and provider (default coingecko, allows coinmarketcap), but lang is only given a default value without explanation. This provides enough context for agent to use parameters correctly.

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 clearly identifies the tool as retrieving live crypto market-cap rankings with specific fields (price, market cap, 24h change, rank movement) and answers a concrete question ('what are the top coins right now?'). It distinguishes itself from sibling tools like get_breaking, get_digest, etc. by focusing on market rankings.

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?

The description implies usage for real-time top-N rankings and specifies the default provider (CoinGecko) with an alternative (CoinMarketCap). However, it does not explicitly state when NOT to use it or point to alternatives among siblings, which is a minor gap.

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