Hardened Google Workspace MCP

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 explains the tool's behavior regarding drive scoping and parameter interactions (e.g., 'drive_id' and 'corpora' defaults), but lacks details on permissions needed, rate limits, pagination beyond 'page_size', or error conditions. It adequately describes what the tool does but misses operational context.

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 well-structured with a clear purpose statement followed by parameter explanations, but it could be more front-loaded. The 'Args' and 'Returns' sections are verbose yet necessary given the complexity. Some redundancy exists (e.g., explaining 'folder_id' defaults twice), but overall it's efficient for a 6-parameter tool.

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 (6 parameters, no annotations, but with an output schema), the description is mostly complete. It covers parameter semantics thoroughly and explains the tool's behavior in different contexts. The output schema handles return values, so the description's brief return statement is sufficient. Minor gaps include lack of error handling or permission details.

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?

The schema description coverage is 0%, so the description must fully compensate. It provides detailed semantics for all 6 parameters, explaining their purposes, defaults, interactions (e.g., 'drive_id' with 'folder_id'), and conditional behaviors (e.g., 'include_items_from_all_drives' when 'drive_id' is not set). This adds significant value beyond the bare schema.

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 verbs ('Lists files and folders') and resources ('supporting shared drives'), distinguishing it from siblings like 'list_docs_in_folder' (specific to Docs) and 'search_drive_files' (search vs. list). It explicitly mentions both personal and shared drive contexts, making the scope unambiguous.

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 explicit guidance on when to use this tool vs. alternatives: it explains the behavior based on whether 'drive_id' is specified (scoped to shared drive) or not (includes 'My Drive' and accessible shared drives). It also implicitly distinguishes from 'list_docs_in_folder' by handling all file types, not just Docs.

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