gemini_generate_image

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

No annotations are provided, so the description carries the full burden. It discloses key behavioral traits: it's a generation tool (implying creation/mutation), supports session-based consistency, and mentions style/character maintenance. However, it lacks details on permissions, rate limits, error handling, or output format (e.g., image type, size). The description doesn't contradict annotations, but it's incomplete for a tool with multiple parameters and no output schema.

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 and front-loaded: the first sentence states the core purpose, and the second adds key functionality (session-based consistency). Both sentences earn their place by providing essential information without redundancy or fluff, making it easy to scan and understand quickly.

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 (7 parameters, no annotations, no output schema), the description is moderately complete. It covers the main purpose and a key feature (session consistency) but lacks details on behavioral aspects like mutation effects, error cases, or output handling. Without annotations or output schema, the description should do more to compensate, but it provides a basic foundation.

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 100%, so the schema fully documents all 7 parameters. The description adds minimal value beyond the schema: it mentions 'session-based image consistency,' which relates to 'conversation_id' and 'use_image_history,' but doesn't provide additional syntax or usage details. With high schema coverage, the baseline is 3, as the description doesn't significantly enhance parameter 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's purpose: 'Generate images using Gemini's image generation capabilities.' It specifies the action (generate) and resource (images) with the technology (Gemini). However, it doesn't explicitly differentiate from sibling tools like 'gemini_edit_image' or 'get_image_history' beyond mentioning session-based consistency.

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 implies usage context through 'session-based image consistency for maintaining style/character across multiple generations,' suggesting this tool is for generating new images with optional consistency features. It doesn't provide explicit guidance on when to use this versus alternatives like 'gemini_edit_image' or 'set_aspect_ratio,' nor does it mention prerequisites or exclusions.

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