List batch jobs

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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds real behavioral detail beyond that: result ordering (newest first), the exact summary fields returned, and the cursor-based forward pagination contract, plus the 'Free' cost signal. It does not say how far back 'recent' reaches or the retention window.

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?

Two short sentences, front-loaded with purpose and payload, followed by the paging rule; the fragment 'Free.' earns its place as a cost signal. No redundant wording.

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 return-value duty and does so by naming the status and count fields as well as the next_* cursors. It is nearly complete for a simple paginated list tool; only the meaning of 'recent' and any page-size default are left to the schema.

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 100%, including the cursor fields referencing next_before_id/next_before_created, so the baseline is 3. The description restates the same cursor contract rather than adding new meaning such as cursor expiry or interaction between the two cursor values.

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 (list batch jobs), plus the ordering (newest first) and the payload (status and succeeded/failed/pending counts). This clearly separates it from the singular get_batch sibling, though it never names siblings explicitly.

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 explains the paging follow-up ('for the next page pass next_before_created and next_before_id from the previous answer') and notes the call is free, which is useful selection context. It gives no when-to-use versus get_batch/get_batch_photos guidance and no exclusions.

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