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

The description goes well beyond the destructiveHint annotation by stating the action is irreversible, requires user confirmation, and only affects open tickets. This is critical risk-related context that annotations alone do not convey.

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 well-structured with headings, but it is redundant: the opening paragraph and the 'When to use' section are nearly identical. This duplication wastes space and deviates from concise writing.

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 single-parameter destructive tool with no output schema, the description fully covers the purpose, prerequisite, constraints, and required confirmation. Nothing critical is missing.

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 describes case_id as 'The case number of the ticket to delete', but the description adds that the ID should be obtained via fetch_open_tickets. This extra source guidance provides meaning beyond the schema's basic type description.

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), the resource (open support ticket), and the prerequisite for obtaining the case_id. It effectively distinguishes this from sibling tools like resolve_ticket or update_ticket by emphasizing irreversible deletion.

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?

It explicitly instructs to call fetch_open_tickets first to get the case_id and notes that only open tickets can be deleted, providing clear when-to-use guidance. However, it does not directly name alternative actions (e.g., using resolve_ticket instead), so it's not a full 5.

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