generate_image

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

No annotations provided, so the description carries full burden. It discloses key behaviors: loop behavior for multiple images, per-model limits (imagen-4-ultra supports 1), file saving to output_dir with fallback defaults, and preview return via return_image. It could mention side effects of file writes explicitly, but overall it is transparent.

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 structured with a one-line summary, detailed Args section, and Returns. It is longer but each sentence is informative. No redundancy; it could be slightly more concise in the Returns description, but overall 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?

With 6 parameters (1 required), no output schema, and no annotations, the description covers all input details, explains default behavior, and describes the return value (list of paths and optional image). It mentions limitations like model-specific constraints. It is complete for an agent to invoke correctly.

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%, so description must explain parameters. It does so thoroughly: prompt (text description), model (friendly aliases with examples), aspect_ratio (with examples and note on model-dependence), n (number with loop behavior), output_dir (default path logic), return_image (preview). This adds significant meaning beyond 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?

The description starts with 'Generate image(s) from a text prompt,' which is a clear, specific verb and resource. The sibling tools 'edit_image' and 'list_models' are distinct, so no confusion.

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?

While the description does not explicitly state when to use this tool versus siblings, the focus on generation from text prompts implicitly distinguishes it from editing or model listing. A more explicit usage guideline would be better but is not necessary given clear sibling names.

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