Generate images

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

With no annotations provided, the description carries the behavioral burden. It adds useful context about output format (inline base64 or download URLs), but does not disclose prerequisites like API key requirements, cost, rate limits, or failure behavior, so its transparency is partial.

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 two focused sentences with the verb+resource front-loaded and zero redundancy. It efficiently communicates purpose, mechanism, and output format.

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 description, combined with a fully described schema and an output schema, gives an agent enough to invoke and interpret results. It lacks explicit usage alternatives and deeper behavioral caveats, but for a simple generation tool it is sufficiently complete.

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 descriptions cover 100% of the parameters, so the baseline is 3. The description adds no additional parameter semantics beyond the schema's own details, though it does reinforce the 'one or more' notion via 'Generate one or more images'.

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 uses a specific verb 'generate' with a clear resource ('images') and source ('text prompt'), which precisely defines the tool's purpose. It also distinguishes itself from sibling tools like vision_analyze and vision_ocr, which analyze or OCR images rather than create them.

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 context for when to use the tool is clear: generating one or more images from a text prompt. However, it does not explicitly state exclusions or mention alternatives such as vision_analyze/vision_ocr, stopping short of the highest level of guidance.

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