batch_images

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

No annotations are provided, so the description carries the full burden. It states that tasks may be generation or edit and that concurrency is controllable, but omits the behavior that matters most for a batch tool: what happens on partial failure (does one bad task abort the rest?), result ordering/correlation to input tasks, and any cost or rate-limit implications.

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, zero waste, with the core purpose front-loaded and the generation-vs-edit distinction immediately after. Nothing is padded.

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?

For a batch tool with no annotations and no output schema, the description covers purpose but leaves out partial-failure behavior and how results map back to the input tasks—information an agent needs to call and interpret this correctly. Adequate but with real gaps.

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% and there are only 2 top-level parameters, so the schema already documents the task fields and the concurrency default of 3. The description adds only the notion of 'concurrency control,' no format or semantics beyond the schema—appropriate baseline of 3.

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?

Names a specific verb+resource (generate or edit multiple images) and clearly scopes it to batching in a single call, which implicitly separates it from the singular generate_image/edit_image siblings. It does not name those siblings explicitly, so differentiation is inferred rather than stated.

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?

Usage is implied: use this when you have several image tasks to run together rather than one at a time. There is no explicit when-to-use/when-not statement, no guidance on when batch beats looping the single-image tools, and no mention of when the concurrency control matters.

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