delete_document

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'delete' but does not state whether the deletion is irreversible, whether it affects the underlying document or just the cached handle, or what happens to associated data. No permissions or side effects are mentioned.

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 and technically concise, but it is essentially a restatement of the tool name with no additional informative content. It under-specifies rather than earning its place with useful detail.

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?

Despite being a simple tool, the description lacks important context such as the distinction between a cached handle and the actual document, potential errors, or any prerequisite conditions. The output schema exists but does not compensate for the missing behavioral context of a destructive operation.

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 sole parameter 'handle' has 0% schema description coverage, and the description only repeats the word 'handle' without clarifying its format, origin, or how it should be passed. This provides minimal added meaning beyond the schema's raw type declaration.

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 the action ('Delete') and the specific resource ('a cached document handle'). This distinguishes it from sibling tools like clear_documents, which likely deletes all documents. The singular 'a handle' aligns with the single required parameter.

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?

No guidance is provided on when to use this tool versus alternatives such as clear_documents. The description does not mention prerequisites, comparisons, or any context for choosing this tool.

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