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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is covered structurally. The description does add a genuinely non-obvious behavioral caveat about how ascending P50 should be read, but says nothing about pagination, result size, or how ranking ties are handled.

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 short sentences, front-loaded with the action, and the interpretive caveat is dense and earns its place. It is efficient, though terse enough that more parameter context could have been added without bloat.

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-value explanation is not required. However, for a five-parameter tool with zero schema description coverage and window/filter objects that materially change results, the description is too thin to be called complete.

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 0% across five parameters, so the description must carry the load. It only loosely gestures at 'metric' ('selected duration statistic') and 'direction' ('Ascending'), leaving limit, window and the repo/workflow/branch filters entirely unexplained.

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 verb and resource ('Rank job groups by a selected duration statistic'), which clearly separates it from sibling stats/list tools. It stops short of explicitly distinguishing itself from the closest siblings such as 9apes_get_job_stats or 9apes_get_run_stats.

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 statement of when to reach for this tool versus the stats siblings, nor any prerequisites. The second sentence is a result-interpretation caveat, not tool-selection guidance, so an agent gets no routing help.

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