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

Annotations already declare read-only, idempotent, non-destructive. The description adds real context beyond them: a scopes requirement, that cursors bind both the job and the item-state filter, and that retained-history cutoffs still constrain results. That is useful operational detail not present in the structured fields.

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 short sentences, purpose front-loaded, no filler. Dense jargon slightly reduces readability but nothing is wasted.

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?

An output schema exists, so return values need not be described, and annotations carry the safety profile. Still, with low schema coverage and many sibling bulk_* tools, the description should do more to explain the state filter and pagination contract.

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 25% (jobId's description is itself tautological, and limit/state/cursor are undocumented). The description partially compensates by tying the cursor to the job and item-state filter, but leaves limit semantics and the meaning of the eight state enum values unexplained.

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?

"Pages through the frozen manifest and secret-safe item outcomes" conveys a paginated list of a bulk job's items, but the language is jargon-heavy and the title does most of the clarifying work. It gives no signal distinguishing it from siblings like bulk_read or bulk_list, so an agent cannot route confidently on the description alone.

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?

"Requires the resolved action's current scopes" is a prerequisite, not a usage guideline. There is no statement of when to reach for this versus bulk_read, bulk_list, or bulk_preview, despite a crowded bulk_* sibling set.

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