share-drive-item

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

Annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds that an optional email is sent and lists roles, but does not explain the effect on existing permissions, whether the action is idempotent, or any side effects beyond the annotation hints. Provides some value but not comprehensive.

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 concise: two sentences plus a tip. It is front-loaded with the core action. Could be slightly better structured (e.g., separating sample into a code block), but overall efficient.

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 (5 parameters, nested body, no output schema), the description is incomplete. It does not mention the return value, error conditions, idempotency, or prerequisites (like permissions on the drive). The user is left without guidance on what happens after the call or how to handle failures.

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 80%, so most parameters are described in the schema. The description adds a concrete example body, explains roles options ('read', 'write', 'owner'), and highlights the 'requireSignIn' parameter. This provides extra context beyond the schema, though not all parameters are explained.

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: 'Send a sharing invitation for a driveItem.' It uses a specific verb ('send') and resource ('sharing invitation'), and distinguishes from siblings like 'create-drive-item-share-link' by focusing on inviting specific users rather than creating a link.

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 tip 'Shares a file or folder with specific users' implies when to use it (for specific users), but lacks explicit guidance on when not to use it or alternatives like 'create-drive-item-share-link' or 'delete-drive-item-permission'. No mention of prerequisites or context.

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