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

With no annotations, the description carries the burden. It discloses that deletion is permanent and bypasses the trash, implying irreversibility. The confirmation instruction also signals high-risk behavior. It does not cover permission side effects or what happens to shared links, but the most critical behavioral traits are stated.

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 two sentences with zero filler. The core action is front-loaded, followed by the critical 'bypasses trash' caveat and the confirmation directive. Every word earns its place.

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 tool, it covers the essential behavioral context (permanence, bypass, confirmation). However, the lack of any description for itemId creates a real gap—an agent does not know what value to supply. There is no output schema, but that is acceptable for delete operations. Overall, adequate but not fully complete.

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?

Schema coverage is only 50%: mailbox has a description, but itemId has none. The description adds no parameter guidance—it never mentions how to identify the file or folder (e.g., what itemId is). It does not compensate for the undocumented itemId, leaving the agent without clear meaning for a required parameter.

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 a specific verb-resource pair: 'permanently delete a Google Drive file or folder.' It also notes 'bypasses trash,' which differentiates it from normal deletion and clarifies scope. Among many sibling delete_* tools, this clearly targets Google Drive items, so an agent can distinguish it without opening schemas.

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?

It provides an explicit usage instruction: 'Ask the user to confirm before calling this,' which is crucial for a destructive operation. It does not mention alternatives or when-not-to-use, but the resource type is unambiguous among siblings. The confirmation requirement is a strong guideline, though exclusions are absent.

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