drive_files_delete

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

The word 'permanently' indicates destructive action, but without annotations the description carries full burden. It fails to disclose permissions required, whether the file must be in trash first, whether it can be recovered, or what side effects occur (e.g., removal from all shared drives). These gaps leave the agent uncertain about the tool's behavior.

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 extremely concise (two words) and front-loaded. Every word is meaningful. Slight deduction for missing structure like bullet points or examples, but for a simple tool this is acceptable.

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 no output schema, the description should explain the return value or confirmation. It does not. Also missing details on error conditions (e.g., if file doesn't exist, if insufficient permissions). The single sentence is insufficient for an agent to fully understand the tool's effect and response.

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 single parameter 'fileId' described as 'The file ID to delete'. The description does not add any meaning beyond the schema. Baseline score of 3 applies.

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.' clearly states the verb and resource, and uses 'permanently' to emphasize irreversibility. It distinguishes from sibling tools that perform other operations on files (copy, create, get, list, update, etc.).

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?

No guidance on when to use this tool versus alternatives. For example, it does not mention any prerequisites (e.g., file must be owned by user), nor does it contrast with a hypothetical trash operation. The description provides no context for appropriate use.

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