delete-drive-item-permission

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

Annotations already set destructiveHint=true, so the description adds value by mentioning the inherited permission constraint. However, it does not disclose error handling, idempotency, or any side effects beyond the deletion itself.

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 concise sentences plus a semantically highlighted tip. All information is relevant and front-loaded. No wasted words.

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?

Describes purpose, prerequisite, and a key constraint. No output schema exists, so lack of return value explanation is acceptable. Could be improved by noting any default behavior or confirmation, but overall sufficient for this operation.

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 covers 100% of parameters with descriptions. The description adds no additional parameter details beyond the tip to use list-drive-item-permissions for the permissionId. Baseline 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?

Title and description clearly state the tool deletes a permission from a drive item. The tip distinguishes it from other delete tools by specifying file/folder context and requiring a permission ID from list-drive-item-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?

Explicitly states when to use: 'Removes a specific permission' and gives prerequisite: 'Use list-drive-item-permissions first to find the permission ID.' Also notes constraint: 'Only permissions that are not inherited can be deleted.' Lacks explicit when-not-to-use or alternative tools, but the guidance is clear.

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