drive_delete

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

No annotations are provided, so description carries full burden. It clearly states the action is permanent, indicating destructiveness and irreversibility. However, it lacks details on permissions, side effects on shared files, or behavior on trashed files. The description adds value beyond the name but could be more comprehensive.

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?

Description is a single sentence with no wasted words. It is front-loaded with the core action and resource, making it easy to parse quickly. Ideal conciseness for a simple 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, the description covers the essential distinction of permanence, which is important given sibling drive_trash. However, it does not describe return values, error conditions, or permission requirements. Given no output schema and no annotations, the description is moderately complete but could be more helpful.

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 only parameter fileId is fully described in the input schema (100% coverage). The tool description does not add any extra meaning or context about the parameter, such as how to obtain it or constraints. 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?

Description clearly states the tool deletes a file permanently from Google Drive. The word 'permanently' distinguishes it from siblings like drive_trash, which moves to trash, and drive_empty_trash. Purpose is specific and unambiguous.

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?

Description implies permanent deletion is for when you want irreversible removal, but does not explicitly state when to use it over alternatives like drive_trash. No when-not-to-use or prerequisite information is provided.

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