Generate Image

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

Annotations already signal that this is a mutating operation. The description adds useful behavioral context by naming the model family (Google Gemini image models), the side effect of saving the image, and the return form (file path). No contradiction with annotations exists.

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 a single, compact sentence that front-loads the core action, indicates the model provider, and states the return value. It contains no filler, repetition, or vague phrasing.

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?

For a simple generation tool with fully documented parameters and an output schema, the description covers the essential behavior and result. It does not mention setup requirements such as authentication, but the presence of a configure_auth sibling and the overall context make this a minor gap rather than a blocking one.

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%: all three parameters already have meaningful descriptions, enums, defaults, and an example for prompt. The description adds no parameter-specific detail, but it does not need to because the schema carries the full semantic load.

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 states a specific verb and resource: 'Create a new image from a text prompt', which clearly differentiates this from editing-oriented siblings like edit_image and continue_editing. It does not explicitly name those alternatives, so it stops short of a 5, but the purpose is unambiguous.

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 usage context is implied: this is for generating a brand-new image from a text prompt, which distinguishes it from image-editing tools. However, there is no explicit guidance about when not to use it or which sibling to choose for editing or continuation tasks.

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