delete_drive_item

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Delete' which is tautological with the tool name and provides no additional traits such as irreversibility, confirmation requirements, cascade effects, or error handling, leaving the agent without critical safety context.

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, front-loaded sentence of five words, making it highly concise and easy to parse. While it is not a tautology, it borders on under-specification, but this is more of a completeness issue than a conciseness issue.

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 destructive nature, lack of annotations, and absence of an output schema, the one-sentence description is entirely inadequate. It fails to explain the relationship to preview_delete_drive_item, any prerequisites, return values, or behavioral caveats, making it unsafe for an agent to use 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 0% description coverage and the description does not elaborate on previewId. The phrase 'previewed drive item' aligns with the parameter name, but it does not explain how to obtain the previewId, its lifecycle, or any constraints beyond the schema's minLength.

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 identifies the action ('Delete') and the resource ('drive item') clearly, and the qualifier 'previewed' distinguishes it from generic delete operations and hints at the preview/apply pattern seen in sibling tools like preview_delete_drive_item. However, it does not explicitly state that this is the apply step following a preview, which leaves slight ambiguity.

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 implies it should be used on a previously previewed item but does not explicitly explain when to use it versus alternatives like move_drive_item or copy_drive_item, nor how it relates to preview_delete_drive_item. There is no exclusionary guidance or context about the required preview state.

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