jira_delete_issue

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

The description mentions that ValueError is raised if in read-only mode or if the Jira client is unavailable, which is useful. However, it does not disclose that deletion is permanent or irreversible, nor does it mention any side effects on linked issues or attachments. With no annotations provided, the description carries the burden but only partially covers it.

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 compact and well-structured, including Args, Returns, and Raises sections. It conveys the essential information without any fluff, making it easy to scan.

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 one parameter and an output schema, the description covers the main action, arguments, return value, and a key exception. However, it could be enhanced by noting irreversibility and potential impacts on related data, but it is already reasonably complete.

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 fully documents issue_key with an example, and the description merely repeats the parameter name without adding additional semantics. Since schema coverage is 100%, the baseline of 3 is appropriate.

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 an existing Jira issue' with a specific verb and resource, which distinguishes it from sibling tools like create, update, or transition. The word 'existing' adds necessary scope.

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?

There is no guidance on when to use this tool versus alternatives, no exclusions, or prerequisites beyond the implicit read-only mode check. It simply states what it does, leaving the agent to infer usage context.

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