List batches

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

Annotations already declare readOnly/idempotent/non-destructive, so the description's job is lighter; it adds real behavioral detail such as pagination termination semantics and the exact per-item fields returned (status text, first shipment's tracking number, per-status counts). One blemish: the opening 'and single labels' is never explained and slightly conflicts with the body, which describes only batches.

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?

Front-loaded with purpose and ordering, then details, then the sibling pointer — a sensible order. There is mild redundancy: 'newest first' appears in both the first clause and again in 'The batches on Pirate Ship's Ship page, newest first'.

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 carries the burden of explaining return shape and does so thoroughly (counts, statuses, tracking number, per-status tallies). The only incompleteness is the unexplained 'single labels' phrase, which leaves ambiguity about whether non-batch labels can appear.

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 100% and already says '0 is the newest page', but the description adds the meaning that an empty list signals exhaustion, which the schema cannot express. Only one parameter exists, so there is little more to say.

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+resource (list batches) plus scope and ordering (newest first, status and tracking counts). It also names get_batch as the single-item counterpart, so an agent can distinguish it from the sibling without opening a schema.

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 final sentence routes detailed single-batch lookups to get_batch, and the 'empty list means no more pages' note tells the agent when to stop paging. It lacks an explicit 'use this when you need an overview rather than counts/stats' exclusion, but the context is clear.

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