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

Discloses cost and unit (15000 base units), the 402 on unpaid calls even with invalid queries, that invalid signed args are rejected before settlement and not charged, that billing occurs only on non-error results, and explains the cached/stale/cacheAgeMs semantics including what stale=true means. Far beyond the readOnlyHint/openWorldHint annotations, and fully consistent with them.

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?

Core behavior is front-loaded, but the bracketed tail block repeats the $0.015 USDC / x402 payment facts already stated two sentences earlier, and the GET /wallet/quick/batch pricing note is tangential to invoking this tool. Roughly a third of the text 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?

No output schema exists, so the description carries the return contract by enumerating the fields (PnL, win rate, score/grade, bot/exchange, net-winner and dormant flags) and the cache metadata. Payment failure modes and validation behavior are also covered, leaving nothing an agent needs to call it correctly.

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 description's 'Pass addresses comma-separated' merely restates the schema's '1 to 10 comma-separated base58 Solana wallet addresses'. No added detail on base58 format or what happens at 11 addresses. Baseline 3 applies.

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 (quick screen), specific resource (Solana wallets, up to 10, batched), the exact metric set returned, the ranking key (realized PnL), and the price. The word 'batch' plus the 'up to 10' cap cleanly separates it from sibling wallet_quick/wallet_profile.

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?

Gives concrete invocation guidance: 'Pass addresses comma-separated', 1-10 limit, and the payment precondition via x402. It does not name a sibling as the alternative for single-wallet or profile lookups, so routing is implied rather than explicit.

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