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

Annotations already declare read-only, idempotent, non-destructive behavior, and the description adds substantial behavioral context beyond them: bounded paging, oversized-group handling that retains population facts and exact API pointers, metric handling rules (zero/negative valid, absent values not zero, units not pooled), rubric score interpretation, and the fact that task measurements change no gate.

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?

It front-loads a purpose sentence, but then packs many caveats into semicolon-heavy clauses and cryptic phrases such as 'Task measurements change no gate.' The density reduces readability even if much of the content is relevant for a complex summary tool.

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?

No output schema exists, so the description must carry return-value context, and it does describe paging, oversized groups, metrics, and rubric scores. However, required identifier parameters and the input cursor/limit semantics are left unexplained, leaving gaps for correct invocation.

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 compensate, but it only indirectly touches pagination ('bounded page', groupPage.nextCursor) and never explains projectId, environmentId, batchId, limit, or the input cursor. It also references taskMetrics, which is not an input parameter in the 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?

States a specific verb, 'Read', and specific resources: complete batch counts, repeated-trial groups, missing evidence, and exact-check denominators. It does not distinguish itself from many siblings such as firedrill_batch, firedrill_batches, or firedrill_report, and the phrasing is dense, but the summary purpose is inferable.

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?

The description gives a pagination usage instruction ('Follow groupPage.nextCursor for more groups') but no explicit when-to-use or when-not-use guidance and no named alternatives among the many sibling tools. Usage remains implied rather than directed.

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