works_share_delete

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

The description discloses a confirm requirement, implying a safety mechanism, but does not explain its purpose or consequences. With no annotations, it fails to mention whether the operation is reversible, if special permissions are needed, or what side effects removing sharing may have on existing permissions.

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, with the main action front-loaded and no extraneous detail. The confirm requirement is stated efficiently, making the description concise and easy to parse.

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?

This is a destructive operation with no annotations and no output schema, yet the description is extremely sparse. It lacks details on what 'remove sharing' entails, whether it deletes all permissions, error conditions, or success indicators, leaving an AI agent under-informed for safe 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?

The description adds minimal parameter meaning: it notes confirm must be true. However, it does not explain file_id or owner_email semantics, and given 0% schema coverage, the description bears the full burden of explaining these parameters but fails to do so.

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 (remove sharing) and the resource (a My Drive folder), using a specific verb. It distinguishes itself from sibling tools like works_share_create by indicating the opposite operation, though it could more explicitly differentiate from works_perm_revoke which also deals 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?

There is no guidance on when to use this tool versus alternatives such as works_perm_revoke or works_share_create. The only hint is 'Requires confirm=true,' which is a prerequisite rather than an indication of appropriate usage context.

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