do

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

With no annotations provided, the description carries the full burden and discloses key behaviors like auto-prefixing '[agent] ' for replies, setting 'confirm=True' to execute shares, and the OAuth setup process. It lacks explicit warnings about destructive actions (e.g., 'overwrite' fully replaces content) and does not mention rate limits or authorization beyond setup.

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, beginning with a general purpose and then detailing operations with bullet-like clarity. It front-loads the main intent and avoids redundancy, though some minor repetition (e.g., listing operations twice) could be trimmed without losing value.

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 (23 parameters, 14+ operations) and no schema descriptions, the description covers major areas: create, edit, email, comments, share, move, and OAuth. It explains when parameters are required but could add more on error handling or return values for edge cases.

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%, but the description adds extensive meaning by grouping parameters per operation (e.g., 'Create: content + title + doc_type', 'Email: draft (to + subject + content)'). It explains the purpose of many parameters in context, though not every parameter (e.g., cc, remove) is individually described.

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 'Act on Google Workspace' and enumerates specific operations (create, move, edit, draft/reply, organise Gmail). It distinguishes itself from siblings 'fetch' and 'search' by being the action-oriented tool, covering creation, modification, and email management.

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 detailed context for each operation, specifying required parameters and behavior (e.g., 'Create: content + title + doc_type' for docs, 'draft (to + subject + content)' for emails). However, it does not explicitly state when not to use this tool versus alternatives, leaving some implicit understanding from the sibling names.

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