Set Drive File Permissions

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

Annotations signal destructiveHint: true; description complements by clarifying it controls link sharing and file-level settings. It provides context that it does not handle individual permissions but does not fully detail what happens to existing permissions. No contradiction with 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?

Four well-structured sentences, no wasted words. Front-loaded with main purpose, then usage guidance, then sibling tool redirect. Highly concise and effective.

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 (5 params, annotations, output schema), the description covers purpose, usage, and limitations. It doesn't explain parameter interactions, but that is acceptable as schema covers individual parameters. Output schema exists, so return values are covered elsewhere.

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 each parameter is documented. The description adds context about the tool's high-level purpose but does not add semantic detail beyond the schema. Baseline 3 is appropriate.

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?

Description clearly states verb ('Sets'), resource ('file-level sharing settings and controls link sharing'), and scope ('for a Google Drive file or folder'). It distinguishes from sibling tools by naming share_drive_file and update_drive_permission for individual 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?

Explicitly says 'high-level tool for the most common permission changes' and directs to alternatives for individual user/group permissions: 'For managing individual user/group permissions, use share_drive_file or update_drive_permission instead.'

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