Set Drive File Permissions

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds some context by noting it's a 'high-level tool for the most common permission changes' and that it handles link sharing. However, it does not disclose potential side effects like overwriting existing file-level settings or what exactly happens when link_sharing is set to 'off.' The description does not contradict annotations.

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 short paragraphs, with the main purpose front-loaded. Every sentence contributes useful information: the first defines the tool, the second clarifies scope and alternatives. No fluff or redundancy.

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?

The description is incomplete due to the confusing requirement of user_google_email. It claims the tool is only for file-level link sharing, yet it requires a user email, which strongly suggests individual user permissions. This contradiction is not addressed, potentially leading an agent to misuse the tool. The description should explain why user_google_email is needed despite the stated scope.

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 100%, so the schema already documents each parameter. The description does not explain why user_google_email is required if the tool is not for individual permissions, which is a notable gap. It adds no extra meaning beyond the schema, so it meets the baseline but does not elevate.

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 function: 'Sets file-level sharing settings and controls link sharing for a Google Drive file or folder.' It uses specific verbs and identifies the resource. It distinguishes itself from sibling tools by labeling itself as a 'high-level tool for the most common permission changes' and explicitly naming alternatives for individual user/group permissions.

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 when-to-use guidance: 'Use this to toggle "anyone with the link" access or configure file-level sharing behavior.' It also specifies when not to use it and names alternatives: 'For managing individual user/group permissions, use share_drive_file or update_drive_permission instead.' This is clear and actionable.

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