drive_delete_file

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

The description discloses the key behavior of moving to trash rather than permanent deletion, which is important for non-reversible decisions. However, it lacks details on authentication requirements, effects on shared files, or behavior when deleting folders with contents. Without annotations, this is somewhat informative but not 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?

The description is a single, concise sentence that front-loads the action and includes the key behavioral note in parentheses. No superfluous 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?

For a simple deletion tool with well-documented parameters and no output schema, the description adequately covers the action and its trash behavior. It could mention return values or side effects but is sufficient for basic use.

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 has 100% description coverage, so the schema already explains both parameters (email and fileId). The description adds no additional parameter context beyond the schema.

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 clearly states the action (delete), the resource (file or folder from Google Drive), and the specific behavior (moves to trash). This is a specific verb+resource that distinguishes it from sibling tools like drive_move_file or drive_search_files.

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 guidance on when to use this tool versus alternatives. It does not mention prerequisites, permissions, or scenarios where moving to trash is preferred over permanent deletion or other operations.

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