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. The description adds a genuinely useful behavioral caveat that annotations cannot express: an empty page does not mean the source was fully inspected, which prevents premature conclusion. It stops short of describing ordering or page-size behavior.

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 tight sentences with the core action first and the pagination caveat second. No filler and nothing redundant with the schema.

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 partially compensates by naming nextCursor, but it does not describe what an evidence record or coverage entry contains, nor any ordering. Adequate for calling the tool, thin for interpreting results.

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 coverage is only 33% and the single documented parameter ('runId (path)') is essentially a restatement. The description does add real meaning for cursor by tying it to a 'nextCursor' value and implying bounded page sizes, but 'limit' and its 1-100 range are never explained in prose.

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 resource (delivered evidence and inspection coverage) scoped to a run, and adds the bounded-paging qualifier. It is reasonably distinguishable from editorial_findings_list and editorial_get_run, though it does not name those siblings directly.

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 operational guidance for pagination ('Pass nextCursor as cursor until done') and a caveat about empty pages. However, it never says when to prefer this over editorial_findings_list, editorial_get_run, or editorial_inspect_source, so tool 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.