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

With no annotations, the description carries the behavioral burden and does so well: it discloses the $0.01 USDC x402 cost, hourly rebuild cadence, and that untracked wallets return 404 and are not charged. It does not cover auth requirements or rate limits, keeping it short of 5.

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 purpose is front-loaded and the trailing operational sentences (addresses, rebuild, 404, cost) are each load-bearing. The central field enumeration is dense and long, but it is informative rather than filler.

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 an output schema present, the description needn't explain return values, yet it adds the operational essentials an agent needs: cost, freshness, and untracked-wallet behavior. Nothing required to call this paid endpoint correctly 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%, so the schema already documents both addr and limit. The description's '(newest 100)' loosely echoes the limit default but adds no syntax, format, or constraint detail beyond what the schema provides, so the 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?

The description names a specific resource (every buy by one Solana copy-leader wallet over the last 14 days) and enumerates the exact return content, so an agent knows precisely what it gets. The verb is implicit in the enumeration rather than an explicit 'retrieve stats', and it never names the sibling sol_wallet_leaders it pairs with, which keeps it from a full 5.

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 only implied: the schema tells the agent where addr comes from (sol_wallet_leaders) and the description notes untracked wallets return 404, which helps a caller decide. But there is no explicit when-to-use-vs-alternatives statement and no comparison against sol_wallet_leaders or the leaderboard siblings.

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