drive_share

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

No annotations are provided, so the description must disclose behavior. It only says 'share', which implies creating a permission, but does not mention side effects (e.g., overwriting existing permissions), authentication needs, or what happens on failure. The schema includes a 'type' parameter but the description does not explain its behavioral implications.

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 a single short sentence that is front-loaded and easy to parse. It is appropriately concise for a simple action, though it lacks structure (e.g., bullet points).

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 interacts with file permissions and has no output schema, the description is incomplete. It does not explain the return value, confirm the sharing outcome, or differentiate from sibling tools. A more complete description would mention that it creates a new permission and list possible side effects.

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 already has a description. The tool description adds no additional meaning beyond the schema. Baseline score of 3 is appropriate as the description does not compensate for any gaps.

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 'Share a file with someone in Google Drive' clearly states the action (share), resource (a file), and target (someone). However, it does not distinguish this tool from siblings like drive_update_permission or drive_list_permissions, which also deal with 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?

No guidance is provided on when to use this tool versus alternatives such as drive_update_permission, drive_remove_permission, or drive_list_permissions. There is no mention of prerequisites, when-not-to-use, or typical use cases.

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