generate_batch

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

With no annotations provided, the description carries the disclosure burden. It usefully reveals parallel execution, one browser tab per prompt, a 4-job limit, and the lack of reference-image support. It does not describe whether the call waits for completion or what it returns, but the behavioral character is mostly clear.

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 three tight sentences with no filler: it states what the tool does, how it behaves, when it is faster, what limits apply, and which sibling to use instead. Every sentence earns its place.

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?

The input side is thoroughly covered by the schema and the description, and the sibling relationship is clear. However, since there is no output schema, the description should state what the call produces or returns, and whether it blocks until images finish generating. That gap prevents full contextual completeness.

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 the parameters are already well documented there. The description adds at most a reminder that each job can carry its own size and basename, but it does not materially deepen the parameter meaning 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 specifies a clear verb and resource: generate several different prompts at once, in parallel, with one browser tab per prompt. It also explicitly distinguishes this tool from generate_image, which removes any ambiguity about its purpose.

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 provides explicit guidance: use this when generating multiple prompts in parallel because it is much faster than repeated calls, and explicitly tells the agent to use generate_image when reference images are involved. This makes the routing decision straightforward.

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