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 the AI model used and editing capabilities but omits critical information like rate limits, authentication requirements, whether edits are destructive to original images, processing time, or error handling. For a complex image editing tool, this leaves significant behavioral gaps.

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 appropriately concise with two sentences that efficiently communicate the core functionality. The first sentence establishes the main purpose, and the second lists key capabilities. No wasted words, though it could be slightly more structured by separating capabilities more clearly.

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 complex image editing tool with 5 parameters, no annotations, and no output schema, the description is insufficient. It doesn't explain what the tool returns (edited images, success/failure indicators, error formats), doesn't mention prerequisites or limitations, and provides minimal guidance on parameter usage despite the schema doing most of the technical documentation.

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 5 parameters thoroughly. The description adds minimal value beyond the schema - it mentions 'multi-image mixing' which relates to the 'images' array parameter, but doesn't provide additional semantic context about how parameters interact or practical usage examples.

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: 'Edit one or more images using Google Gemini 3.0 (Nano Banana Pro).' It specifies the verb ('Edit'), resource ('images'), and technology used, but doesn't explicitly differentiate from sibling tools like 'describe_image' or 'generate_image' beyond mentioning editing capabilities.

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 'generate_image'). It mentions capabilities like 'style transfer, object manipulation, and multi-image mixing' but doesn't clarify whether these are exclusive to this tool or available in alternatives.

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