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

Annotations already cover read-only, idempotent, non-destructive, open-world, so the bar is lower; the description adds real value beyond them by disclosing the 15-day lookback, the ranking basis, the semantics of headline_pnl_sol (net cash flow with open positions at cost), the verdict enum values, and a caveat that past performance is not predictive. It does not say how many wallets are returned or whether the window is rolling.

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, front-loaded with scope and ranking, then field semantics, then a caution. The closing clause 'read the reasons before copying any wallet' slightly restates the verdict explanation, but nothing else is wasted.

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 no output schema, the description carries the burden of explaining return values and does so for the two headline fields plus the verdict. It omits result size, whether the window is rolling or fixed, and any other row fields, which leaves a modest gap for a leaderboard tool.

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?

The tool takes zero parameters, so the baseline is 4. The description instead spends its space documenting the shape and meaning of returned fields, which is a reasonable substitute given there is no output 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?

States a specific verb and resource (read the public Solana wallet leaderboard) plus the ranking metric and time window (net SOL, 15-day). The leaderboard-of-wallets scope is clearly distinct from the sibling tools get_wallet_summary (single wallet) and get_token_summary (token), so an agent can route without opening a schema.

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 description implies the usage context (screening wallets before copying them) and gives one behavioral instruction: read the verdict reasons before acting on a wallet. It never explicitly says when to use this versus get_wallet_summary, nor when not to use it (e.g. for a single known address).

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