delete_document

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

Clearly states permanent deletion from memory and disk, and irreversibility. With no annotations, description carries full burden and does so well. Could mention potential side effects or failure modes.

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, front-loaded with action and effect. No wasted words.

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?

Single parameter, no output schema, no annotations. Description adequately covers purpose and behavioral traits. Could mention success/failure indicators, but sufficient for a destructive 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?

Only one parameter (doc_id) with schema coverage 100%. Description adds no extra meaning beyond schema's 'Document id'. Baseline of 3 is appropriate.

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?

Description clearly states action: 'Permanently delete a document', specifies resource ('document'), and notes irreversibility. Distinguishes from sibling tools like create_document or open_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?

Implies caution with 'Cannot be undone', but no explicit when-to-use or alternative guidance. Could mention that other tools like archive or move exist for non-destructive actions.

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