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 but offers minimal behavioral insight. It states the action (listing) and return type (formatted list), but doesn't disclose permissions needed, rate limits, pagination behavior (despite a 'page_size' parameter), or whether it's read-only/destructive. The mention of 'formatted list' adds some context, but key operational details are missing.

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 brief and front-loaded with the core purpose in the first sentence. The second sentence about return values is somewhat redundant given the output schema, but overall it's efficient with minimal waste.

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 moderate complexity (3 parameters, no annotations, but with output schema), the description is incomplete. It covers the basic action and return format, but lacks parameter explanations, usage guidelines, and behavioral details. The output schema mitigates some gaps, but the description doesn't provide enough context for effective tool selection and invocation.

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 but fails to do so. It doesn't explain any of the three parameters (user_google_email, folder_id, page_size), their purposes, formats, or constraints. The baseline would be lower than 3 due to poor coverage, and the description adds no parameter information beyond what's inferred from the tool name.

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 verb ('Lists') and resource ('Google Docs within a specific Drive folder'), making the purpose unambiguous. It distinguishes from siblings like 'list_drive_items' by specifying Google Docs only, though it doesn't explicitly contrast with 'search_docs' or other listing tools.

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 'list_drive_items' or 'search_docs'. The description mentions the scope (Google Docs in a folder) but doesn't specify prerequisites, exclusions, or comparative use cases with sibling tools.

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