generate_image

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

No annotations are provided, so the description carries full burden. It mentions the return format (Markdown block with URLs and revised prompt) and that editing uses references, but does not disclose potential side effects, authentication needs, rate limits, or whether originals are modified. This is adequate but incomplete.

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 concise with two sentences of overview followed by a structured Args and Returns section. Every sentence is informative, no waste, and it is well-organized.

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 8 parameters and no output schema or annotations, the description covers parameters and return value adequately. It explains the dual generate/edit mode. However, it lacks error conditions, size limits, or additional behavioral constraints, leaving some gaps.

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 0%, so the description must add meaning for all 8 parameters. It explains each parameter's purpose, including the dual role of prompt, the model options, how image paths/urls serve as references, and provides examples for aspect_ratio. This fully compensates for the missing schema descriptions.

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 clearly states the tool generates or edits images, specifying the action and resource. It distinguishes between generation (no references) and editing (with references), and is distinct from sibling tools like generate_video.

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 explains when to pass image paths/URLs for editing versus generating new images. It mentions combining multiple references, but does not explicitly state when not to use this tool or compare to alternatives, though sibling context makes it clear.

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