jira_delete_issue

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

No annotations are provided, so the description must disclose behavioral traits. It only states the delete action and optional subtask deletion, but omits critical details such as irreversibility, permissions needed, or impact on linked issues. The description is insufficient to fully inform the agent of consequences.

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 very concise (two sentences) and front-loaded with the core action. However, it slightly underutilizes the available space for additional useful context, making it efficient but minimal.

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 simplicity of the tool (2 parameters, no output schema, no nested objects), the description is mostly complete for a delete operation. It covers the essential functionality and optional subtask deletion, though it could mention the return value (e.g., empty response on success).

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% with descriptions for both parameters. The description does not add meaning beyond what the schema provides; 'Optionally delete its subtasks' echoes the deleteSubtasks parameter. Baseline score of 3 applies as schema already covers parameters adequately.

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 'Delete a Jira issue' with a specific verb and resource, distinguishing it from other deletion tools among siblings (e.g., jira_delete_comment, jira_delete_attachment). The optional subtask deletion is also mentioned.

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?

No guidance on when to use this tool versus alternatives (e.g., jira_update_issue, jira_transition_issue). Context of use or exclusions are not provided.

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