gemini-media-mcp

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states the action ('edit') and inputs but lacks critical details: whether edits are destructive (overwrite original?), authentication needs, rate limits, output format (though output schema exists), or error handling. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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 highly concise and front-loaded: two sentences that directly state the tool's function and required inputs. Every word earns its place, with no redundancy or fluff, making it easy for an agent to parse 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 moderate complexity (editing with a prompt), 100% schema coverage, and presence of an output schema, the description is minimally adequate. It covers the basic action and inputs but lacks behavioral context (e.g., edit implications, error cases) that annotations would normally provide. With output schema handling return values, completeness is borderline but not fully sufficient for safe use.

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 three parameters ('prompt', 'imagePath', 'model') with descriptions. The description adds minimal value beyond the schema, mentioning 'path to the source image' and 'description of the desired changes' but no additional semantics like prompt formatting tips or path requirements. Baseline 3 is appropriate when 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: 'Edit an existing image using a text prompt.' It specifies the verb ('edit'), resource ('existing image'), and method ('text prompt'), distinguishing it from siblings like 'generate_image' (creates new) or 'animate_image' (adds motion). However, it doesn't explicitly differentiate from 'compose_images' (which might involve editing multiple images), keeping it from a perfect score.

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. It mentions 'edit an existing image' but doesn't specify scenarios (e.g., minor tweaks vs. major transformations) or contrast with siblings like 'compose_images' for multi-image edits. Without such context, users must infer usage from tool names alone.

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