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

The description discloses core behavior ('generate a share link') and optional email-gating. However, it does not mention that this is a write operation (creating a resource), what the return format is, or any side effects. With no annotations, the description carries the full burden but falls short.

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?

Two sentences, 55 words, front-loaded with the main action. Every sentence adds value, no fluff. Efficient and well-structured.

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?

Despite having 6 parameters and no annotations, the description omits the return value (presumably the share link) and does not differentiate from the sibling drive_invite tool. This leaves gaps for an agent to know what to expect and when to choose this tool over similar ones.

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 coverage is 100%, so baseline is 3. The description adds value by explaining email-gating ('only a specific person can access it') and the permission levels ('Humans open this link to view, comment, or edit files'). Does not elaborate on max_uses or expires_in, but overall adds meaningful context.

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 'Generate a share link for a workspace or specific file,' specifying the verb and resource. It distinguishes from sibling tools like drive_delete or drive_comment by focusing on sharing.

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 implies the tool is for generating share links but does not explicitly state when to use it versus alternatives like drive_invite (a sibling tool). No exclusions or when-not-to-use guidance provided.

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