Share Drive file

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

With no annotations, the description must fully disclose behavior. It only says 'Share a file', but does not mention that this modifies existing sharing permissions, that it may overwrite prior roles, that it sends a notification by default, or that the account parameter selects which Google account to use. This lack of behavioral detail leaves significant gaps for a mutation tool.

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?

A single, front-loaded sentence exactly states the core purpose with zero filler. Every word earns its place, and the description is sufficiently concise for the tool's simplicity.

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 rich schema coverage, the description fails to provide essential context for practical use, such as whether existing permissions are replaced, whether the account parameter is required for multi-account scenarios, or how notifications behave. For a tool with no output schema and no annotations, this under-specification leaves the agent with incomplete guidance for invocation.

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 all five parameters have descriptions in the schema. The tool description adds no extra meaning beyond 'by email and role', which aligns with the schema. Thus, the baseline of 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?

The description clearly states the action (share), the resource (a file), and the intended recipient (by email and role). This uniquely distinguishes it from other Drive tools like google_drive_update (which modifies file metadata) or google_drive_delete, making the purpose immediately evident.

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 granting access to a specific user via email and role, which provides clear context for when to use it. It does not explicitly mention alternatives or when not to use it, but the brevity and clarity make the intended use obvious within the suite of Drive tools.

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