batchGenerate

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states the basic action and does not mention how the batch is processed, whether failures are handled per-prompt, if output is returned directly or asynchronously, or any side effects. This is a significant gap for a batch operation.

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?

The description is a single, front-loaded sentence that effectively communicates the tool's purpose without unnecessary words. It is concise and well-structured, though brevity in other dimensions is penalized separately.

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?

Despite the schema being fully documented, the description lacks important contextual information such as what the tool returns, how it handles multiple prompts (parallel vs sequential), and any prerequisites or error behavior. With no output schema and no annotations, this incompleteness is notable.

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?

The schema descriptions cover both parameters (prompts and baseOptions) fully, so the additional value from the description is minimal. The description's 'different prompts' aligns with the prompts array but adds no new syntax or format detail beyond the schema.

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 clearly states the verb ('Generate'), resource ('images'), and scope ('multiple', 'different prompts'), which distinguishes it from the sibling generateImage that implies single-image generation. It is specific and instantly conveys the tool's core function.

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?

The description implies usage for batch image generation with multiple prompts, but it does not explicitly state when to prefer this over generateImage or other siblings. There is no mention of exclusions or alternative tools, so the guidance is only implied.

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