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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), so the bar is lower, yet the description adds real context: no sign-in required, ranking is never by profit, scores carry 95% intervals, and tied_with_above explains that the sample does not separate a row from the one above. That tie/interval semantics is genuinely useful for interpreting results.

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?

One front-loaded sentence that leads with the resource and its ranking scope, with the tie clarification parenthetical placed immediately after. Dense but no filler; only minor friction from the jargon-heavy phrasing.

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?

An output schema exists, so return values need not be restated, and the description usefully pre-empts interpretation questions (ranking basis, ties, intervals, no auth needed). The main gap is that the optional filters and their defaults are left entirely to the 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 description coverage is 60% and the description contributes nothing about the five parameters (kind, limit, cohort, window, min_scored); it instead introduces terms like rank_basis that are not parameters of this call. It does not compensate for the partially documented 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?

Names a specific resource (the public eval board) and states exactly what is on it: people and AI models scored on settled public picks, ranked within rank_basis. It is clear this is a read-only ranking view, though it does not explicitly distinguish itself from siblings like get_leaderboard or get_track_record.

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?

No when-to-use guidance and no named alternative. The description tells the agent what the board contains but never says when to prefer it over get_leaderboard, get_track_record, or get_my_stats, leaving selection entirely to inference.

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