drive_files_delete

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

Annotations already provide destructiveHint: true and readOnlyHint: false. The description reinforces this with 'permanently,' adding the nuance of irreversibility. It does not contradict annotations, and it adds a small amount of behavioral context beyond what annotations state, though not substantial detail about side effects or auth requirements.

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, front-loaded sentence with zero filler. It conveys the core action immediately and is appropriately sized for a one-parameter tool.

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?

For a simple delete operation with one parameter and annotations covering safety, the description is nearly complete. It mentions permanence, which is key. It omits details like permission requirements or error behavior, but these are not critical for basic usage, and the annotations fill the safety gap. Slight room for improvement in noting that deletion is irreversible (already implied) or that associated metadata is removed.

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 coverage is 100% with a clear description for fileId: 'The file ID to delete.' The description adds no further semantic detail about the parameter, so it relies on the schema. Baseline 3 is appropriate given high coverage.

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 states a specific action and resource: 'permanently delete a file.' It clearly distinguishes this from siblings like drive_files_update, copy, export, and even drive_permissions_delete, since the resource and verb are explicit. The word 'permanently' adds specificity about the outcome.

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?

The description gives no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. While it's clear this is the delete operation for files, there is no mention of conditions like ownership or permission checks, nor whether a soft-delete alternative exists. It is minimally sufficient but lacks routing context.

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