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

Annotations already declare readOnly, idempotent, non-destructive and open-world, so safety is covered. The description adds genuinely useful non-obvious traits: results are sorted by total rugs, each entry breaks down per-pad counts, and a 'PAD HOPPER OF THE DAY' entry is appended — an agent would not expect that extra non-ranked row from the schema. It does not cover result size or pagination behavior interacting with n. (Score reflects the additive return-shape detail against a high annotation baseline.)

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?

Roughly 60 words for a moderately complex board tool, front-loaded with the definition of a pad hopper. The middle sentence, 'Each leg = that pad's rugged of resolved, with its N,' is telegraphic to the point of ambiguity, which costs a point on structure even though nothing is padded.

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 one optional parameter, no output schema, and annotations covering the safety profile, the description supplies what an agent actually needs: the population definition, the ranking rule, the per-pad breakdown, and the extra daily-highlight row. Terms like 'resolved' and 'N' remain unexplained jargon, a minor residual gap.

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% and the single parameter n is fully documented ('rows, 1-100 (default 25)'). The description adds nothing about n, but the baseline is 3 when the schema carries the parameter documentation.

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 resource with an exact qualifying criterion: developers who rugged on 2+ named launchpads, ranked by total rugs. The enumerated pad list and the leaderboard framing make it clearly distinct from siblings like groundtruth_scoreboard or groundtruth_kol_board. It lacks an explicit verb ('list'/'rank') at the front, keeping it short of a 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?

Provides a routing cue to a sibling: 'groundtruth_creator_flag carries the same tag per dev (pads.hopper)' tells the agent to go there for per-developer lookups while this tool is the cross-pad board. No explicit exclusions or negative conditions are given, so it stops at clear context rather than full when/when-not guidance.

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