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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so safety is covered. The description adds meaningful context beyond that: it is paper-trading only ('Paper only.'), results are 'before fees', 'losers counted', and vetoes include 'the reason and the market-cap move since' — useful methodology disclosure the annotations do not convey.

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?

Two sentences, front-loaded with the resource and its ranking basis, then the alternative tab. Dense with jargon ('graded result', 'Skeptics', 'losers counted') but each clause carries distinct information about mode or constraint 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?

For a 2-param read-only board with no output schema, the description covers both modes, both parameters, the trading basis, and the fee caveat. Nothing an agent needs to select a tab or set the window is missing; only return-shape details are absent, which is acceptable without an output schema.

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 0%, so the description carries the full burden and largely does: it defines the two tab values (board, vetoes) and the day window ('over 7 or 30 days'), matching the two integer/string params and their defaults. It is the primary source of parameter meaning here.

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 (PumpPill Arena) and clearly distinguishes its two modes: 'swarms ranked by graded result' (tab=board) vs 'tokens their Skeptics refused' (tab=vetoes). The verb is implicit ('ranked', 'refused') rather than a clean action verb, and it does not name or contrast with siblings like agents_leaderboard, but the two-tab structure is legible.

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 parenthetical '(tab=board)' and '(tab=vetoes)' effectively route the agent to the correct mode and its contents, which is implied usage guidance. However there is no explicit when-to-use/when-not statement and no reference to alternative sibling tools for similar leaderboard data.

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