documents_delete_document

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

No annotations are provided, so the description carries the full burden. It only says 'Delete a stored document by its UUID,' without disclosing whether deletion is permanent, what happens if the UUID doesn't exist, or any required permissions. For a destructive operation, this is insufficient.

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 concise sentence with no unnecessary words or repetition. It gets straight to the point.

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?

Given this is a destructive delete operation with no annotations and no output schema, the description should provide more context about permanence, error handling, or side effects. The simplicity of the tool doesn't excuse the lack of behavioral disclosure. An agent might incorrectly assume the operation is non-destructive or reversible.

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 schema already provides 100% coverage for the single parameter 'id' with description 'Document UUID to delete.' The tool description's phrase 'by its UUID' adds no new meaning beyond the schema. Baseline 3 is appropriate because schema does the heavy lifting.

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'), the target ('a stored document'), and the key identifier ('by its UUID'). This distinguishes it from sibling tools like documents_add_document, documents_search_documents, and documents_list_documents.

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 usage (delete a document when you have its UUID), but it doesn't explicitly state when to use this tool versus alternatives or provide any exclusionary guidance. There is no mention of when not to use it or that it should be preferred over update/search for deletion purposes.

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