preview_delete_drive_item

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Preview deleting' implies a non-destructive action but does not state that no deletion occurs, what the preview returns, or any side effects. This is a significant gap for a tool that could be confused with an actual delete.

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 with no fluff, which is concise. However, it is under-specified and lacks any structure (e.g., examples, notes), making it minimally adequate but not well-rounded.

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 has 3 required parameters, no annotations, and no output schema, a one-sentence description is wholly inadequate. It does not explain what the preview shows, how to interpret results, or any operational context. The description is far too shallow for effective tool selection and invocation.

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 adds no parameter information. The three required parameters (driveId, itemId, name) are unexplained, and 'name' is especially ambiguous given the schema's unusual $ref definitions. The description does nothing to compensate for the lack of schema documentation.

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 states 'Preview deleting a drive item' with a specific verb and resource, clearly distinguishing this from the sibling tool 'delete_drive_item' and other preview actions. It directly conveys what the tool does.

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?

Usage is only implied by the 'preview' prefix and the existence of 'delete_drive_item' as a sibling, suggesting this is a safe dry-run before actual deletion. However, there is no explicit guidance on when to use this tool versus alternatives or when not to use it.

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