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

The description explicitly warns that deletion is permanent, which is the most critical behavioral trait for a destructive operation. However, with no annotations, it does not mention authorization requirements, idempotency, side effects, or error behavior, leaving meaningful gaps.

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 sentence with no filler. It efficiently states the action, object type, and required input.

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 one-parameter deletion tool, the description adequately covers the action, object, and input mechanism. It omits return behavior and error cases, but given low complexity and fully documented schema, it is sufficiently 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 100%: the single required id is already documented as 'Document ID.' The description repeats 'by ID' and expands 'document' to doc/word/note, but adds no semantic detail beyond what the schema already provides.

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 the specific verb 'Permanently delete' and clearly identifies the resource as a document (doc, word, note) by ID. This distinguishes it from sibling delete_sheet and delete_slide_presentation tools.

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 is for documents, not sheets or slides, and requires an ID. It does not explicitly mention alternatives or exclusions, but the sibling tool names make the scope reasonably clear.

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