Batch Generate

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

No annotations are provided, so the description carries the full behavioral burden. It does disclose one meaningful trait — parallel execution — which affects latency and error-handling expectations, but says nothing about partial failures, per-prompt error reporting, cost/rate implications, or whether shared model/quality settings apply to all outputs.

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?

A single front-loaded sentence with no filler; the parallel/batch nature is stated first, which is the key decision-relevant fact.

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 described. However, for a batch mutation-style tool with zero annotations and five parameters, the absence of any statement about partial-failure behavior or per-prompt result mapping leaves a real gap for an agent deciding whether to batch or loop over generate_image.

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%, so all five parameters including the prompts array, model, quality preset, aspect ratio, and output format are already documented inline. The description only echoes that generation is driven by a prompt list and adds no constraints or format detail beyond the schema, making the baseline 3 appropriate.

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 ('Generate'), resource ('images'), and distinguishing scope ('multiple ... in parallel from a list of prompts'). This implicitly separates it from the sibling generate_image, but it never names that sibling, so the differentiation requires the agent to infer it.

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 only implied: 'a list of prompts' suggests batching rather than one-off generation, but there is no explicit 'use generate_image for a single image' routing, no guidance on batch size (1-10 lives only in the schema), and no mention of when a batch is a poor choice.

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