generate_images

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

With no annotations, the description does carry real behavioral weight: it warns that higher concurrency may hit rate limits, promises one result per job in order, and states that failed jobs carry an 'error' key — useful partial-failure semantics. It says nothing about write side effects on disk (overwrite), cost of parallel runs, or what happens when some jobs fail and others succeed beyond the error field.

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?

Three short blocks — purpose, job shape, concurrency/returns — with the batch framing front-loaded and no filler sentences. The inline dict notation is dense but readable for an agent.

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 spelled out. But for an 8-parameter mutation tool with zero annotation coverage and zero schema descriptions, six parameters (notably tolerance and chroma_key, which control output pixels) remain entirely opaque, so the definition is not complete enough to call it reliably.

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% and the tool has 8 parameters, so the description must compensate. It fully specifies the critical `jobs` item shape (prompt, output_path, reference_images, per-job overrides) and explains `concurrency` (default 3, rate-limit risk), but leaves trim, max_size, overwrite, tolerance, chroma_key, and reasoning_effort completely undefined — the qualified names alone convey no meaning.

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 with a clear scope modifier: 'Generate several images in parallel', plus a concrete use case ('every pose of a sprite set'). It implicitly separates itself from the singular sibling generate_image via the batch framing, though it never names the sibling explicitly.

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 sprite-set example implies when the batch tool is preferable to the single-image tool, but there is no explicit 'use this instead of generate_image when...' routing, and no stated prerequisites such as an authenticated session.

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