delete_document

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

No annotations are provided, so the description carries the transparency burden. It discloses the destructive and irreversible nature ('Permanently delete', 'cannot be undone'), which is critical safety information. It doesn't mention permissions, cascading effects, or failure modes, but the core destructive behavior is clearly conveyed.

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 extremely concise, consisting of two short sentences that front-load the action and immediately provide the key safety warning. No words are wasted.

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?

While the tool is simple and has an output schema, the description lacks parameter semantics and usage guidance. It also doesn't address prerequisites or side effects beyond permanence, making it incomplete for an agent to confidently invoke.

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 two parameters (doctype, name) with zero schema descriptions, and the tool description doesn't explain either parameter. This is a significant gap since the description must compensate when schema coverage is low.

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 clearly states 'Permanently delete a document' using a specific verb ('delete') and resource ('document'), distinguishing it from sibling tools like create_document, get_document, and update_document. The addition of 'Permanently' clarifies the scope and irreversibility of the operation.

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 provides no explicit guidance on when to use this tool versus alternatives. The permanent, irreversible warning implies caution but doesn't specify contexts or exclusions, leaving usage to be inferred from the tool name and the warning.

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