Google Workspace MCP Server

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 describes the search scope and result format, but doesn't mention important behavioral aspects like authentication requirements, rate limits, pagination behavior beyond page_size, or whether this is a read-only operation. The description adds some value but leaves significant gaps.

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?

Well-structured with clear sections (description, Args, Returns). The description sentence is efficient, and parameter explanations are necessary given the 0% schema coverage. Could be slightly more concise in the corpora explanation, but overall earns its place.

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 complexity (6 parameters, 0% schema coverage, no annotations) and the presence of an output schema, the description does well. It thoroughly documents parameters and describes the return format. However, for a search tool with no annotations, it could better address behavioral aspects like authentication, rate limits, and error conditions.

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 compensates excellently by providing detailed parameter explanations. Each parameter gets clear semantics: user_google_email is 'required', query 'supports Google Drive search operators', page_size has a default, drive_id behavior is explained, include_items_from_all_drives has default and condition, and corpora gets detailed usage guidance with efficiency recommendations.

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 ('searches') and resource ('files and folders within a user's Google Drive, including shared drives'). It distinguishes itself from sibling tools like 'list_drive_items' by emphasizing search functionality rather than simple listing.

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 (searching within Google Drive) and mentions scope (including shared drives). However, it doesn't explicitly state when NOT to use it or name specific alternatives like 'list_drive_items' for non-search scenarios.

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