Gemini Image MCP

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. It mentions some constraints (e.g., 'up to 4K resolution,' 'up to 14 reference images') but lacks critical details like rate limits, authentication requirements, cost implications, error handling, or output format. For a generative AI tool with potential side effects, this is insufficient.

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, efficient sentence that front-loads the core purpose and key features. It avoids redundancy and wastes no words, though it could be slightly more structured (e.g., separating purpose from constraints).

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 (generative AI with multiple parameters) and lack of annotations or output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., image data, file path), error conditions, or usage limits, leaving significant gaps for an agent to operate effectively.

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 already documents all parameters thoroughly. The description adds minimal value beyond the schema—it mentions 'up to 4K resolution' and 'up to 14 reference images,' which are partially covered in the schema's descriptions. Baseline 3 is appropriate as the schema does most of the work.

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 an image using Google Gemini 3.0 (Nano Banana Pro).' It specifies the verb ('Generate') and resource ('image'), and mentions key capabilities like resolution and reference images. However, it doesn't explicitly differentiate from sibling tools like 'describe_image' or 'edit_image' beyond the core generation function.

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 provides no guidance on when to use this tool versus its siblings ('describe_image' and 'edit_image'). It mentions technical capabilities (e.g., up to 4K resolution, reference images) but doesn't indicate scenarios where this tool is preferred over alternatives or any prerequisites for use.

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