works_perm_revoke

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

The description discloses the need for confirm=true and the inability to bulk delete, which is useful behavioral information. However, it does not explain what happens when confirm is false, required prerequisites, or potential errors, leaving some ambiguity for a destructive operation.

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 three short sentences, front-loaded with the primary action, and contains no unnecessary words. Every sentence adds meaningful information about the operation.

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 (6 parameters, no output schema, no annotations), the description is too sparse. It omits the role of sharedrive_id, user, and folder_id, and does not clarify return values or failure modes, making it incomplete for an agent to safely invoke.

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?

With 0% schema coverage, the description must explain all parameters, but only perm_id and target_email are mentioned. The required sharedrive_id parameter is not described, and user, folder_id, and confirm (beyond 'required') lack semantic detail. This is insufficient for a 6-parameter tool.

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 verb 'Delete' and the resource 'permission', specifying the two identifier methods (perm_id or target_email). This unambiguously distinguishes it from sibling tools like works_perm_grant and works_perms_list.

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?

It gives practical usage context by stating that bulk delete is unsupported and that confirm=true is required, which helps the agent know constraints. It does not explicitly mention alternatives or when not to use this tool, but the guidance is clear enough.

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