generate_image_batch

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

No annotations present, so description must reveal behavior. It covers concurrency, fire-and-forget vs blocking, and return of job IDs, but omits error handling, cost, or rate limits.

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 tight paragraphs, front-loaded with key behavior. Every sentence adds value with no redundancy.

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?

Given 11 parameters, only two are mentioned. Output schema exists but not described. Core flow is covered, but many details missing for a complete understanding.

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 0%, yet description only explains wait and max_concurrent. The other 9 parameters (model, resolution, etc.) are not described, leaving the agent to infer from their names.

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?

Description clearly states verb 'queue' and resource 'image batch', with parallel execution. Distinguishes from sibling 'generate_image' by focusing on batch and concurrency.

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?

Explicitly explains when to use wait=False vs wait=True, and mentions polling with queue_status/list_jobs. Lacks exclusions or alternatives but provides clear context for usage.

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