drive_files_delete

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

Annotations already declare destructiveHint=true and readOnlyHint=false, clearly signaling mutation. The description adds the qualifier 'permanently', reinforcing irreversibility. However, it does not disclose additional behavioral traits such as whether the deletion affects shared permissions or fails for non-existent files.

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 sentence containing only essential information. Every word serves a purpose, and there is no redundancy or extraneous content.

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 simplicity and the presence of annotations (destructiveHint), the description adequately covers the core action. However, it could mention that the operation does not return a response body or clarify the source of the fileId (though the schema supplies that). Overall, it is mostly complete for a straightforward delete.

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 input schema provides full coverage for the single parameter fileId with a description. The tool's description does not add extra meaning beyond what the schema already states, so the baseline score of 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?

The description 'Permanently delete a file' uses a specific verb ('delete') and resource ('file'), directly and unambiguously stating the tool's action. It clearly distinguishes itself from sibling tools like drive_files_copy or drive_files_update by specifying the destructive nature of the operation.

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 provides no explicit guidance on when to use this tool versus alternatives (e.g., trashing a file or using a delete with confirmation). The word 'permanently' implies irreversibility, which offers implicit context, but no when-not-to-use or alternative tool names are mentioned.

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