Delete issued document

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

The description adds 'Irreversible' and 'Permanently', which reinforce the destructiveHint annotation and provide additional context about the consequence of deletion. It does not contradict annotations and adds value by warning the user about the non-recoverable nature, though it doesn't disclose other behavioral details like auth requirements.

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 extremely concise, using only two short sentences. Every word is purposeful, with the key action and consequence front-loaded. No redundant or unnecessary content.

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 delete tool with two well-described parameters and annotations conveying destructive and idempotent hints, the description is sufficient. It covers the purpose, method, and consequence. It could theoretically mention error cases or return behavior, but for a deletion operation this is largely optional.

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 descriptions cover both parameters at 100%, so the description adds little beyond what the schema already provides. The phrase 'by ID' aligns with the document_id parameter but does not introduce new semantic details.

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: 'Permanently delete an issued document by ID.' It uses a specific verb (delete), identifies the resource (issued document), and specifies the parameter (by ID). This distinguishes it from sibling tools like get_issued_document and update_issued_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 when to use the tool (when you need to delete an issued document by ID) but provides no explicit guidance on when not to use it or mention of alternatives. There is no reference to sibling tools or exclusions, so it falls short of a 4.

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