Google Workspace MCP VE

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 states this is a list operation (implying read-only) and describes what information is returned (revision ID, modified time, etc.), which is helpful. However, it doesn't mention pagination behavior (despite the page_size parameter), rate limits, authentication needs, or error conditions, leaving gaps in behavioral understanding.

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 perfectly concise and well-structured: two sentences that each earn their place. The first sentence states the core purpose, and the second provides both return value details and usage guidance. There's zero wasted text and it's front-loaded with the main functionality.

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 value documentation), no annotations, and moderate schema coverage, the description does a good job. It explains the tool's purpose, return data, and usage context. The main gap is lack of behavioral details like pagination or error handling, but the output schema reduces the completeness burden.

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 67% (2 of 3 parameters have descriptions), so the schema does substantial work. The description doesn't add any parameter-specific information beyond what's in the schema (e.g., it doesn't explain user_google_email's purpose or file_id format). With decent schema coverage, the baseline 3 is appropriate as the description doesn't compensate for the 33% gap but doesn't detract either.

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 specific action ('List revision history') and resource ('for a Drive file'), distinguishing it from siblings like 'get_drive_file_content' or 'restore_drive_revision'. It precisely defines what the tool does without being vague or tautological.

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 explicitly provides usage guidance by stating 'Useful before calling restore_drive_revision', which tells the agent when to use this tool in relation to an alternative/sibling. This creates a clear workflow context without needing to list all possible alternatives.

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