Delete Document

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states that deletion is permanent, cannot be undone through the API, and requires user confirmation — all critical behavioral traits for a destructive tool.

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?

Two sentences with no filler. The operation is stated first, followed immediately by the destructive warning and the required user-confirmation behavior. Every sentence 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 one-parameter destructive operation, the description is complete: it names the resource, explains the consequence, and gives the required safety protocol. Since an output schema exists, return-value documentation is not needed.

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 single required parameter, document_id, is never described in the prose, and schema description coverage is 0%. The description says 'a document' but does not explicitly connect it to the document_id parameter or explain what identifier is expected. The parameter name provides some clue, but the description does not compensate for the lack of schema guidance.

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 a specific verb and resource: 'Permanently delete a document from the library.' It clearly distinguishes this from sibling operations like deleting a folder or updating a document.

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 clearly instructs the agent to confirm with the user before calling because the operation is destructive and irreversible. It does not explicitly enumerate alternative tools or when not to use it, but the deletion purpose and confirmation gate are strong context.

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