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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds genuine context beyond them: the three upstream sources (latest close record, minepoa's grading list copy, POAScan's tx archive), the derived definitions (answer gap over 3 h or under 20 answer txs, seal txs under 25% of the last-3-closes median), and an explicit negative contract: 'Never a pending seal blob or score.' That negative scope is exactly the kind of thing annotations cannot 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?

No filler, and the 'Counts only' constraint is front-loaded, but the body is one long run-on sentence with nested parentheticals that is hard to parse on first read. Content earns its place; the structure does not help the reader.

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 no output schema, the description carries the return-shape burden and largely does so, naming the returned metrics (answers, longest_gap_s, seals, baseline) and the per-close breakdown. Undefined domain jargon (birth band, birth panel, seal, quorum) is left to shared vocabulary, which is the only real 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?

There is a single optional parameter with 100% schema description coverage, so the schema already carries the segment/archive semantics. The description never mentions segment at all, adding no meaning beyond the schema; baseline 3 applies.

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?

It states a specific verb+resource: 'Counts only, from the latest close record' about the grading queue, and enumerates the exact aggregates returned (pending answers by closes waited, near-quorum, expiring, per-close neutral_answer/neutral_grading). The final sentence 'Use it to see where the grading queue is stuck' pins the intent. It never names a sibling, so an agent must infer its difference from get_pending_by_epoch / get_pending_horizon on its own.

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?

'Use it to see where the grading queue is stuck' gives a use context, but there are no exclusions or pointers to alternatives, despite several nearby queue-oriented siblings (get_pending_by_epoch, get_pending_horizon, get_grade_history). The 'Counts only' framing implies it is not for detail lookups, but that is inference rather than an explicit rule.

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