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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so safety is covered. The description adds genuinely useful methodology context the annotations cannot: losers are counted, results are before fees, and each row includes rules, exits, best/worst, and a copy link. It does not mention refresh cadence, entry count, or pagination.

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 compact sentences, front-loaded with the identity of the ranking and its basis, then the row contents. No filler or repetition of the name/title, though the phrasing is denser than it needs to be.

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 read-only, single-optional-parameter tool with no output schema, the description covers what is ranked, how, the window options, the caveats, and the return shape per row. Only minor operational details (count of rows, how to interpret ties or the copy link) are absent.

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 schema documents the lone 'days' parameter at 0% description coverage and only says integer/default 7, but the description supplies the meaningful values ('over 7 or 30 days'), effectively defining the parameter's accepted domain. It stops short of stating what happens for other integer values.

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?

Names a specific resource ('Agent leaderboard') and states what it aggregates: trading agents written in plain English in PumpPill's Telegram bot, ranked by graded Robinhood Chain results. It is distinguishable from most siblings (rh_* tools, room_calls), though it never explicitly contrasts itself with near-neighbors like outcomes_measured or best_calls.

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?

There is no when-to-use or when-not-to-use statement, and no alternative is named. An agent must infer from the word 'leaderboard' that this is the ranking view rather than the raw-calls view, with no guidance on how it relates to outcomes_measured, best_calls, or room_calls.

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