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

Annotations already mark the tool destructive and non-read-only. The description adds meaningful behavioral context by emphasizing irreversibility ('cannot be undone') and requiring user confirmation before invocation. This goes beyond what the structured hints alone convey and helps the agent understand the severity and consent requirement.

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 short sentences, front-loaded with the action and permanence, and the confirmation warning is placed where it is likely to be seen. Every word earns its place; there is no filler or redundant restatement of the tool name.

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 one-parameter destructive action, the description covers the core details: what is deleted, that deletion is permanent, that user confirmation is mandatory, and that it cannot be undone. The existence of an output schema and the annotations cover safety and idempotency hints. It does not discuss permission requirements, but this is a minor gap for such a straightforward tool.

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 description coverage is 100%, so the single file_id parameter is already fully documented. The description names the resource type (Google Drive file) and adds the deletion context, but it does not add new parameter-level details. Baseline 3 is appropriate given complete schema coverage.

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 clear verb and resource: 'Permanently delete a file from Google Drive.' It explicitly signals permanence, which distinguishes this deletion tool from siblings like move_file or block_file. No ambiguity remains about 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?

The description gives clear operational context: it is for permanent deletion and must not be invoked without prior user confirmation. It does not explicitly name alternative tools for non-permanent actions, so it stops short of a full when/not comparison, but the guidance is unambiguous and actionable.

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