generate_image

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

With no annotations provided, the description carries the full burden of behavioral disclosure and does so thoroughly. It states that the prompt is sent to Gemini as an image generation request, that generated images are saved to disk and appended to a cumulative HTML gallery, and that the tool returns absolute paths plus the gallery path.

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 well-structured and front-loaded with the core purpose, followed by important side-effect and return information, then parameter details. Every sentence adds meaningful value without unnecessary padding.

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 covers the essential behavior, side effects, return information, and both parameters. It also points to list_models for model selection, making the tool self-contained and complete for invocation despite the lack of annotations.

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 compensate for both parameters, and it does. The prompt parameter is explained with specific visual-detail guidance, and the model parameter is documented with defaults and a pointer to list_models.

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 and resource: generate one or more new images from a text prompt. It clearly distinguishes this from edit_image by emphasizing new image generation from a text prompt, and from list_models by targeting actual image creation.

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 gives clear context for when to use the tool: when a new image should be generated from a text prompt and saved/viewable via the gallery. It does not explicitly name edit_image as the alternative for modifying existing images, so it stops short of full when-to-use vs alternatives guidance.

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