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

With no annotations, the description carries full behavioral burden and does so richly: it discloses the ranking methodology (replay of 60 buys through a fixed exit, shrinkage toward pooled mean), refresh cadence (rebuilt hourly), failure behavior (503 and not charged if older than 3h), and cost ($0.05 USDC via x402). These are exactly the operational traits an agent needs before calling a paid, snapshot-based tool.

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?

Front-loaded with the core identity before methodology, cost, and staleness details. The methodology sentence is dense but every clause (exit rules, shrinkage, fees, cap) explains the ranking and thus earns its place; nothing is redundant.

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 paid snapshot leaderboard with an output schema present, the description covers the remaining gaps: what gets returned conceptually (sample size, win share, sell pattern), data freshness, failure semantics, and pricing. An agent has everything needed to decide whether and how to call it.

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?

There is a single optional parameter whose schema description coverage is 100% ('Max rows, 1-50 (default 50)'), so the schema already documents it fully. The description adds nothing about the limit parameter, making the baseline score of 3 appropriate.

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 names a specific resource and ranking metric: 'Top Solana copy-trade leaders ranked by shrunk replay EV,' with a clear explanation of the ranking construction. It is easy to distinguish from generic leaderboards, though it never explicitly contrasts itself with closely named siblings like sol_wallet_copy_stats or sol_callers_leaderboard, which an agent must infer.

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?

Usage context is implied (find wallets worth copy-trading) but there is no explicit when-to-use/when-not guidance and no routing to alternatives such as sol_wallet_copy_stats for a single wallet. The staleness rule ('refused at 503 if older than 3h') is a precondition, not usage guidance.

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