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

Annotations already declare readOnly/idempotent/non-destructive, so the bar is lower, and the description adds real behavioral context beyond them: the pagination contract (cursor must be replayed with the same run/scope), the fact that large records are returned as metadata pointers rather than inline, and the caveat that reassessment records are not extra executions. This is meaningful disclosure for a list tool.

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?

Three dense sentences, front-loaded with the resource and then the operational rules. No filler, though phrases like "frozen evidence digests" and "exact authenticated API metadata pointers" are terse to the point of being opaque without prior domain familiarity.

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?

For a read-only, non-paginated-schema-free list tool this covers pagination and pointer behavior, which are the main risks. It still leaves the assessment record's shape and the meaning of projectId/environmentId/limit unexplained, and there is no output schema to fill that 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 description coverage is 0% across 5 parameters, so the description must compensate. It only gestures at run and "scope" via prose, names a cursor as "nextCursor" while the actual schema property is "cursor" (a naming mismatch), and says nothing about limit, projectId, or environmentId semantics or constraints.

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+resource: paging "versioned assessments of one run," with the additional content types (frozen evidence digests, evaluator usage). An agent can distinguish it from firedrill_reassess and firedrill_report reasonably well, though the description never explicitly contrasts those siblings.

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?

Gives genuine operational guidance — "Follow nextCursor with the same run and scope until null; a page is not the entire history" — which is the key usage rule. However, it never says when to prefer this over firedrill_report, firedrill_summary, or firedrill_reassess, so alternative selection is left to inference.

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