Gemini Image MCP

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

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions 'maintaining previous context' and 'allowing repeated modifications,' which gives some behavioral insight, but lacks critical details like whether this creates a persistent session, what authentication or permissions are needed, rate limits, or what happens if the session fails. For a tool with 6 parameters and no annotations, 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 concise with two sentences that directly state the tool's purpose and key behavioral trait. It's front-loaded with the main action and wastes no words, though it could be slightly more structured by explicitly mentioning session initiation.

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 (6 parameters, no annotations, no output schema), the description is incomplete. It doesn't explain what the tool returns, how sessions are managed, error handling, or prerequisites. For a tool that likely creates a stateful session, this leaves significant gaps for an AI agent to understand its full behavior.

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 no additional parameter semantics beyond what's in the schema, such as explaining interactions between parameters (e.g., how 'imagePath' and 'prompt' work together). Baseline 3 is appropriate when the schema does the heavy lifting.

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 as 'starting a multi-turn image editing session that maintains previous context and allows repeated modifications.' It specifies the verb ('start') and resource ('image session'), but doesn't explicitly differentiate it from sibling tools like 'continue_image_session' or 'edit_image' beyond the 'start' aspect.

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 alternatives like 'continue_image_session' or 'edit_image.' It mentions maintaining context for repeated modifications, but doesn't clarify if this is the only way to achieve that or when to choose it over other image tools.

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