Google Docs MCP Server

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

No annotations are provided, so the description carries full burden. It states the tool inserts an image, implying a write/mutation operation, but doesn't disclose behavioral traits like required permissions, rate limits, whether the image is embedded or linked, what happens if the URL is invalid, or the response format. The description adds minimal context beyond the basic action.

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 directly states the tool's purpose with zero wasted words. It's appropriately sized for a straightforward tool and front-loads the key information.

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 mutation tool with 5 parameters and no annotations, the description is minimal. It covers the basic action but lacks behavioral context, usage guidelines, and detailed parameter semantics. The existence of an output schema helps, but the description doesn't reference it or explain what the tool returns. It's adequate for a simple tool but has clear gaps in completeness.

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 60%, with 3 of 5 parameters documented. The description adds that the URL must be 'publicly accessible', which provides context for the 'image_url' parameter beyond the schema's basic description. However, it doesn't explain the semantics of 'index' (1-based positioning) or optional 'width'/'height' parameters, leaving gaps in parameter understanding.

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 action ('insert'), the resource ('inline image'), and the source ('from a publicly accessible URL'). It distinguishes from sibling tools like 'insert_image_from_resource' by specifying the URL source rather than a resource ID.

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?

No guidance is provided on when to use this tool versus alternatives like 'insert_image_from_resource'. The description mentions the URL must be 'publicly accessible', but this is a parameter constraint rather than usage guidance. There's no mention of prerequisites, error conditions, or typical use cases.

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