jira_delete_issue

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

Annotations already mark this as destructive, non-read-only, and idempotent. The description adds useful behavioral context beyond those hints: routing is restricted to a governed connector authority, `effect` is verified by Spring, and `approval_ref` is used when resuming a write after approval. This gives the agent meaningful expectations about auth, verification, and approval flow.

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 and reasonably concise: it opens with the operation identity, then gives the routing constraint, followed by a clear parameter list. Each parameter entry is short and earns its place. It could be tighter by stating the actual deletion behavior in the first sentence, but it avoids unnecessary filler.

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 that this is a destructive write operation with seven parameters and zero schema descriptions, the description is not complete enough for an agent to invoke it correctly. It never explains how to specify which issue to delete inside `arguments`, what the required argument shape is, or what confirmation/guardrails exist beyond the generic `effect` and `approval_ref` fields. The routing and approval context is useful, but the core invocation payload is left underspecified.

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?

Since schema description coverage is 0%, the description bears the burden of explaining parameters, and it does add value with one-line semantic labels for `arguments`, `project_id`, `project_ref`, `connector_account_ref`, `idempotency_key`, `effect`, and `approval_ref`. The central `arguments` parameter, however, is only described as a generic JSON string without indicating which Jira issue fields or keys are expected, which prevents full comprehension.

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 identifies the tool as the Jira connector operation `delete_issue` and states the platform tool as `jira.delete_issue`, which clearly conveys that it deletes a Jira issue. It is distinguishable from sibling Jira operations like `jira_delete_automation_rule` and `jira_delete_webhook` by the resource name. However, the description never explicitly says 'deletes the specified Jira issue', relying partly on the tool name for meaning.

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 is provided about when to use this tool versus alternatives. The description only explains routing constraints ('Routes only through the exact project/account governed connector authority') and parameter meanings, but never states that this tool should be selected to permanently remove a Jira issue, nor does it mention not to use it for deleting automation rules, webhooks, or other entities.

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