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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the bar is lower. The description adds genuine behavioral context beyond them: that maxResults switches the tool into a self-cursor-following mode that pages internally at most 50 at a time and returns a summary envelope. It does not explain 'stoppedBy' or any rate/consistency traits.

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?

A single dense sentence with no filler; the primary paging behavior and the maxResults variant are both front-loaded, and the parentheticals carry real information rather than restating the name.

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 the return envelope need not be explained, and the description still names its fields. The remaining gap is around operational preconditions (batch state, whether items are only available after completion) and the meaning of stoppedBy, which leaves the agent guessing for a 5-parameter tool.

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 20%, so the description must compensate, and it largely does: id is identified as the batch taskId, limit is bounded at 50, cursor is explained as the paging position, and maxResults is described as auto-following cursors. Only 'debug' is left entirely undocumented in both places.

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 and resource: paging through a batch's results, keyed by taskId, with explicit cursor/limit semantics. It is distinguishable from get_batch (metadata) and get_batch_errors in the sibling list, though it never names those siblings to disambiguate 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?

It guides the choice between two invocation modes (manual cursor paging vs. maxResults auto-follow), which is real usage guidance. However it gives no guidance on when to use this tool rather than get_batch, wait_batch, or get_batch_errors, and no prerequisites (e.g. whether the batch must be finished).

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