Google Workspace MCP Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions the return format ('A formatted list'), which adds some value, but doesn't cover critical aspects like pagination behavior (despite a 'page_size' parameter), authentication requirements, rate limits, error conditions, or whether this is a read-only operation. For a tool with no annotations, this leaves significant gaps in understanding its behavior.

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 extremely concise and well-structured: two sentences that directly state the purpose and return value without any fluff. Every word earns its place, and the information is front-loaded, making it easy to scan and understand 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 that there's an output schema (which handles return values), no annotations, and low schema coverage, the description is minimally adequate but has clear gaps. It covers the basic purpose and return format, but doesn't provide enough context for parameters, usage guidelines, or behavioral traits. For a tool with three parameters and no annotations, it should do more to be fully helpful.

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 0%, so the description must compensate for undocumented parameters. It only mentions 'specific Drive folder', which loosely relates to 'folder_id', but doesn't explain the other two parameters ('page_size' and 'user_google_email') or their purposes. The description adds minimal value beyond what's inferred from parameter names, failing to adequately address the coverage gap.

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: 'Lists Google Docs within a specific Drive folder.' It specifies the verb ('Lists'), resource ('Google Docs'), and scope ('within a specific Drive folder'). However, it doesn't distinguish this tool from sibling 'list_drive_items' or 'search_docs', which appear to have overlapping functionality, preventing 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. There are multiple sibling tools like 'list_drive_items', 'search_docs', and 'search_drive_files' that might serve similar purposes, but the description offers no comparison or context for choosing this specific tool. The only implicit guidance is the folder-specific focus, but this isn't explicit.

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