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

Annotations already cover read-only, idempotent, open-world, non-destructive, but the description adds material economics and failure behavior that annotations cannot express: 0.003 USDC per call via x402 on Base or Solana, no account or API key, invalid input refused before payment, failed runs never charged, and a PaymentRequired response when unpaid. That is exactly the extra context an agent needs before committing to a paid call.

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 scope enumeration is front-loaded in the first sentence and the payment and sample-lookup details follow in a logical order. It is longer than typical, but nearly every clause carries either scope or payment information an agent would otherwise have to probe for.

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?

With one optional parameter, no output schema, and strong annotations, the definition covers what remains: what data comes back, what payment is required, where the HTTP equivalent lives, and how to get a free sample. Nothing blocking a correct first call is missing.

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% and the single limit parameter is already documented as "items per list, 1-20 (default 10)", so the schema does the heavy lifting. The description only echoes this indirectly through the sample URL (limit=10) and does not clarify that limit applies per list rather than in total, so it adds little beyond the schema.

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?

Names a concrete verb and a rich set of resources: most searched coins, top 24h gainers/losers among the 250 largest, global market cap and BTC dominance, and last-hour trending Solana tokens with price/liquidity/organic volume. That scope cleanly separates it from siblings like crypto_price (single asset quote) and solana_token_check (token due diligence).

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 framing "what the crypto market is doing right now" tells the agent this is the market-overview call rather than a single-asset lookup, and it explicitly routes to the sibling get_example for a free preview before paying. It stops short of naming when to prefer crypto_price or solana_token_check instead, so no true exclusion guidance.

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