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

Annotations already declare readOnly, idempotent, non-destructive and closed-world behavior, so safety is covered. The description adds real behavioral context beyond that: which fields each batch carries (id, slug, output format, template id) and the default page size of 25, implying cursor pagination. It does not cover ordering or rate limits.

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 with no filler: trigger and scope first, return shape and pagination second, exclusion last. Every sentence carries distinct information and the most important framing is front-loaded.

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 spelled out further, and annotations carry the full safety profile. For a zero-required-parameter, read-only list tool, the description supplies everything an agent needs: trigger, scope, pagination default, and the boundary against get_batch.

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 the schema descriptions already explain limit (defaults to 25), cursor (nextCursor of previous page), and projectId (all projects when absent). The description restates the project scoping and page-size default but adds no format or edge-case detail beyond the schema, so the baseline of 3 applies.

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?

Specific verb (list) plus resource (processed-image batch metadata) and an explicit scope qualifier (optionally scoped to a project). The closing sentence 'Not for one batch's variant files and links' separates it from get_batch, so an agent can distinguish it from siblings 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?

Gives a clear trigger condition ('Use this when the user wants to list existing processed-image batch metadata') and a negative boundary excluding the single-batch variant/links case. It stops short of naming the alternative tool explicitly (get_batch), so the routing is described rather than directly pointed at.

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