delete_document

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

With no annotations provided, the description must disclose behavioral traits itself. It states the action ('Delete') but fails to mention the permanence of the operation, any authorization requirements, or potential side effects on related data. This is insufficient 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?

The description is concise and front-loaded with the main action. The Args section is neatly formatted and adds value without unnecessary words. It is slightly terse but appropriately sized for the tool's simplicity.

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 having an output schema, the description omits critical context for a destructive operation: it does not warn that deletion is irreversible, mention error scenarios (e.g., nonexistent document), or note any cascading effects on knowledge base indexes or related data. This is a significant gap.

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 only provides a type 'string' with no description. The tool description compensates by specifying that document_id is a 'UUID of the document to delete', adding semantic meaning and fully covering the single parameter.

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 the specific verb 'Delete' and identifies the resource as 'a document from the knowledge base', clearly distinguishing it from sibling tools like add_document, update_document, and get_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?

The description implies its purpose through the verb 'Delete' but offers no explicit guidance on when to use it over alternatives, no prerequisites, and no exclusions. It is adequate but relies on the tool's name and obvious intent.

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