jira_issues_delete

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

Annotations already include destructiveHint=true, but the description adds that deletion is irreversible and recommends admin confirmation. It also describes the return format ({success, issue_key}). This adds useful context beyond the annotation.

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?

Three sentences, each essential. Front-loaded with the core action. No redundant 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?

Given the output schema exists, the description covers key behavioral traits (permanence, caution, subtask behavior, return format). Could mention that issue must exist or error handling, but sufficient for a destructive operation.

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 description coverage is 100% (both parameters described). The description briefly adds context for delete_subtasks ('Also delete all subtasks') and mentions the default, but this largely mirrors the schema. Baseline 3 is appropriate as the description adds minimal extra semantics.

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 a Jira issue permanently'. The verb 'Delete' and resource 'Jira issue' are specific, and 'permanently' distinguishes it from soft-delete or other operations. It is distinct from sibling tools like update, transition, etc.

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 includes cautionary guidance: 'Use with caution: confirm with an admin before deleting.' However, it does not explicitly state when to use this tool versus alternatives (e.g., when a user might want to close rather than delete). No when-not-to-use guidance is provided.

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