generate_batch

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

With no annotations, the description carries the full burden and does meaningful work: it discloses the queuing model, that all jobs share one Flow tab, that no extra tabs open, the 8-job ceiling, and that upscale applies globally. It leaves open what happens if one job fails mid-batch and whether partial results are returned, which matters for a batch mutation.

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?

Four short sentences, front-loaded with the core purpose, then the queuing mechanics, then limits. No filler; the capitalized DIFFERENT and SAME efficiently carry the key constraints.

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?

There is no output schema, so the description's note that 'everything is collected at the end' is doing necessary work, but it does not say what the return looks like (paths, per-job status, filenames). For a tool with a global option and per-job overrides, that is a modest gap rather than a fatal one.

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 coverage is 100%, so the schema already documents every parameter including fit, format, out_dir, background and the per-job fields. The description adds one genuinely useful cross-parameter fact, that 'upscale applies to all' jobs rather than per job, and notes per-job independence for size, filename and reference images; otherwise it restates 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?

States a specific verb and resource (generate multiple prompts) and adds a distinguishing qualifier: 'several DIFFERENT prompts in one call' versus the single-prompt sibling. It never names generate_image explicitly, so the contrast with the sibling 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?

Gives clear context for when this tool is appropriate: multiple different prompts that should share one Flow tab and be queued rather than run sequentially. It stops short of explicit exclusions such as 'use generate_image for a single prompt' or guidance on when upscale_image should be called separately instead.

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