gdrive_delete_file

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

With no annotations provided, the description carries the full behavioral burden. It discloses that only empty folders can be deleted, which is useful, but it omits whether deletion is permanent, what happens on failure, whether files go to trash, and what sync side effects occur. This is insufficient for a destructive operation.

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 short but visibly incomplete, ending mid-clause with an em-dash and no continuation. It is under-specified rather than concise, and the missing remainder likely contains essential context about the synced Drive path.

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 destructive tool with no annotations and no output schema, the description does not cover return values, failure modes, target identification, or safety caveats. The only edge-case information is the 'empty folder' restriction, which is not enough to let an agent invoke this confidently.

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 zero parameters, so there is nothing for the schema to document. However, for a delete operation, the absence of a target parameter is conspicuous, and the description never explains how the file or folder to delete is identified. The description adds little meaning beyond the tool's name.

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 uses a specific verb ('Deletes') and identifies a clear resource ('a file or an empty folder') and scope ('synced Google Drive folder'). This distinguishes it from OneDrive or local delete tools by domain, though it doesn't explicitly name what it is not.

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 guidance on when to use this tool over alternatives, no mention of prerequisites, and no exclusion criteria beyond the 'empty folder' restriction. The truncation also cuts off the contextual clause, leaving the intended usage implied rather than stated.

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