drive_delete

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

Disclosures beyond destructiveHint annotation: no recovery, requires authentication, and mandates confirmed parameter. No contradiction with annotations.

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?

Very concise: one sentence for purpose, then usage rules. No redundant words. Front-loaded with critical info.

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?

Covers all critical aspects for a destructive tool: permanence, no recovery, authentication, confirmation requirement, and alternative. No output schema needed as return is obvious.

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?

Adds meaning beyond schema: explains path must be absolute starting with '/', stresses confirmed must be true and user confirmation required. Even with 100% schema coverage, this significantly aids correct usage.

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?

Description clearly states the tool permanently deletes files/folders with no trash step or recovery. It distinguishes from sibling drive_trash by specifying reversible deletion alternative.

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 tells when to use (permanent deletion needed) and when not (use drive_trash for reversible). Provides clear instructions: require confirmed=true, show exact path to user, get explicit confirmation.

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