Delete issue

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

The phrase 'This is destructive' is a meaningful warning, and with no annotations the description carries the full burden of behavioral disclosure. However, it does not explain permanence, permission requirements, cascading effects, or what happens after deletion.

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 short sentences with no filler. The action is stated first, and the caution follows immediately; every word contributes useful information.

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 one-parameter destructive tool with no output schema, the description captures the essential facts: what action to perform and that it is destructive. Missing details like permissions or response shape are peripheral given the low complexity of this 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?

Schema coverage is 100%: issueKey is already documented with a clear description and example (PROJ-123). The tool description adds no extra parameter meaning, so it relies on the schema baseline.

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?

States a specific action verb ('Delete') and resource ('an issue'), clearly distinguishing it from siblings like create_issue, update_issue, and transition_issue. No ambiguity about what this tool does.

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?

Provides no explicit guidance on when to use this tool versus alternatives, no context, prerequisites, or exclusions. The intended use must be inferred entirely from the tool name and the word 'Delete'.

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