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

With no annotations, the description must carry the full burden. It discloses the useful operational constraints — a 20-token batch ceiling and the accepted input formats — and 'Current' implies a read-only snapshot. It does not state data freshness/latency, rate limits, or how invalid or unknown tokens are handled.

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?

Three sentences, all load-bearing: what it returns, how to identify tokens, and when to use it. The batch limit and format examples are front-loaded before the use-case guidance.

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-value shape need not be explained. The description covers scope, input formats, and batch limits, which is sufficient for a single-parameter read tool; only error/failure behavior remains unaddressed.

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 0% and the single 'tokens' parameter is a bare string, so the description must compensate — and it does, listing symbol (BTC, ETH, SOL, PEPE), CoinGecko id, and chain:contract address forms with worked examples. It does not say explicitly whether multiple tokens are comma-separated or how the 20-max is enforced.

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+resource ('Current USD price and 24h change') with concrete scope: up to 20 tokens per call, three accepted identifier formats with examples. The word 'current' implicitly separates it from crypto_price_history and crypto_candles, but no sibling is named explicitly.

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?

'Use for portfolio valuation, trading decisions or answering what a token costs now' gives clear usage context and steers toward spot pricing rather than historical data. It stops short of naming alternatives (crypto_coin_info, crypto_price_history, exchange_ticker) or stating when not to use it.

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