Hardened Google Workspace MCP

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

With no annotations provided, the description carries full burden and does an excellent job disclosing behavioral traits. It explains how different file types are handled (Google Docs exported as text, Office files parsed, others downloaded with UTF-8 decode attempt), what happens with binary files, and that it returns plain text with metadata header. This goes well beyond basic parameter documentation.

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 structured and front-loaded: purpose statement first, then bullet points for file type handling, then parameter explanations, then return value. Every sentence earns its place - the bullet points are essential for behavioral transparency, and the Args/Returns sections are necessary given the poor schema coverage. No wasted words.

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 (handling multiple file types with different processing logic), no annotations, 0% schema coverage, but having an output schema, the description is remarkably complete. It covers purpose, behavioral details, parameter semantics, and return format. The output schema handles the return structure, so the description appropriately focuses on the transformation logic and usage context.

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?

With 0% schema description coverage, the description fully compensates by explaining both parameters in the 'Args' section. It clarifies that user_google_email is 'The user's Google email address' and file_id is 'Drive file ID', providing essential semantic context that the bare schema lacks. This is exactly what's needed when schema coverage is minimal.

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 with specific verb ('Retrieves') and resource ('content of a specific Google Drive file by ID'), including scope ('supporting files in shared drives'). It distinguishes from siblings like get_drive_file_download_url (which returns a URL rather than content) and get_doc_content (which is specific to Docs rather than all Drive files).

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 clear context about when to use this tool by specifying it retrieves file content from Google Drive, including shared drives. It doesn't explicitly state when not to use it or name alternatives, but the context is sufficient for an agent to understand this is for extracting readable text from Drive files rather than metadata or URLs.

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