Create batch

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

The annotations already declare destructive, non-idempotent, open-world behavior, and the description adds genuinely new context: provider scopes, locks and credit consumption apply, a confirmation gate is mandatory, and only one submission is accepted. It stops short of describing what happens on failure or whether a created batch can be undone, but it meaningfully exceeds the annotation coverage.

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, front-loaded sentences with no padding; the operational constraints are stated crisply. The leading raw endpoint "POST /v5/batches" is somewhat wasteful since it just restates the tool, but overall the text is tight and earns most of its space.

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?

This is a complex, nested tool with up to 100 image items, huge modification schemas, no output schema, and no annotations about credits or job lifecycle. The description supplies useful operational framing (credits, locks, confirmation) but omits batch semantics, size limits, whether the call is async, and how results are retrieved, leaving material gaps for correct invocation.

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% — account, confirm, payload ("Use payload or payload_file exclusively") and payload_file are all documented in the schema itself. The description only echoes the confirmation idea, adding no syntax, format, or constraint detail beyond the structured fields, so the baseline 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?

The description gives an HTTP endpoint ("POST /v5/batches") and the title restates "create batch," so the verb+resource is present but the actual purpose is never explained — it never says a batch renders multiple images from multiple payload items. It also fails to distinguish this from close siblings like create_image or the preview_render_batch/apply_render_batch pair, leaving an agent to infer the concept.

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?

"Mandatory confirmation before provider execution; one submission only" states a prerequisite, which is useful, but there is no guidance on when to choose this tool over list_batches, get_batch, create_image, or the preview_render_batch/apply_render_batch flow. No when-to-use or when-not-to-use context is offered.

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