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

Annotations already declare safety (readOnly, idempotent, non-destructive, closed-world), and the description adds useful behavioral context: results are persisted, pagination is bounded, and cursor iteration continues until done. It does not contradict annotations and clarifies the follow-up reading pattern, though it does not describe return shape.

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 two sentences, front-loaded with the core operation and pagination instruction, followed by the natural next step. Every sentence carries actionable meaning with no filler.

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 paginated read tool with no output schema and three parameters, the description covers pagination mechanics and the subsequent read action needed to get integration decisions and unresolved gaps. It stops short of describing the list items' fields, but that is reasonable given the instruction to read individual runs for details.

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?

With 0% schema description coverage, the description compensates well for cursor by explaining that nextCursor should be passed as cursor until done, and it implies project scoping and bounded pages. It does not explicitly name the limit parameter or clarify its maximum (the schema already declares maximum 20), so the coverage is strong but not complete.

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 specific verb and resource: recovering persisted editorial runs for a project in bounded pages. It distinguishes itself from a single-run read via the follow-up instruction to 'read each relevant run' afterward, though it does not explicitly name the sibling tool for that follow-up.

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 provides concrete pagination guidance: pass nextCursor as cursor until done, then inspect each relevant run for decisions and gaps. This is clear procedural context, but it does not state when to prefer this tool over alternatives such as editorial_list_briefs or editorial_get_run.

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