Generate Image with Gemini

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

The description discloses output delivery (inline preview, save to disk) and default model, but with no annotations, it does not cover potential behavioral traits like rate limits, authentication needs, or the ability to handle reference images. It provides some useful context but is not comprehensive.

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?

Two sentences, front-loaded with the key action. Every sentence adds value: first states the core function, second adds output details. No wasted words.

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 the tool's complexity (8 parameters, 3 enums, no output schema), the description is too brief. It omits critical capabilities like reference images, search grounding, aspect ratio control, and the thoughtSignature editing feature. The user must rely entirely on the schema for understanding, which is inadequate for a high-level overview.

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 100%, so baseline is 3. The description does not add any extra meaning beyond what the schema already provides for parameters. It does not mention any parameter details, so it neither harms nor significantly enhances understanding.

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 an image using specific models and mentions output behavior (inline preview, saving to disk). The verb 'generate' and resource 'image' are specific, and the tool name itself distinguishes from siblings like edit_image.

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?

No guidance on when to use this tool over alternatives such as edit_image or generate_svg. The description does not provide any context about appropriate scenarios or exclusions.

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