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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the read-only safety profile is established. The description adds useful context beyond annotations: rows are tied to the current analysis and rowId has specific semantics. It does not discuss pagination or output shape, but those are less critical given the strong annotations.

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?

The description is three short sentences with no filler. The primary purpose is front-loaded, and each sentence adds relevant information: scope, rowId semantics, and downstream revision guidance.

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 tool with rich annotations, this is adequate but not complete. It leaves limit/offset semantics unexplained, does not define what 'current analysis' refers to, and introduces basis.originalRevision without context. An agent could call it correctly, but some follow-up interpretation is required.

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 only 25%, so the description must compensate for undocumented parameters. It does clarify rowId semantics, but limit and offset are left without meaningful explanation beyond their schema constraints. projectId is already described in the schema, so the description adds little for the remaining parameters.

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 clearly states a read operation on 'matrix rows bound to the current analysis' and provides a useful disambiguation: rowId identifies a matrix row, not a requirement. It does not explicitly differentiate itself from sibling read tools such as read_requirement_coverage, but the resource and scope are reasonably clear.

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?

It gives clear context that rows are bound to the current analysis and adds a practical downstream instruction to reuse basis.originalRevision when requesting changes. However, it does not explicitly state when not to use this tool or name an alternative, so it falls short of 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.