Xray Delete Test

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

Annotations already flag destructiveHint, idempotentHint, and readOnlyHint=false, so the safety profile is covered. The description still adds real value by disclosing the non-obvious side effect that the Jira issue itself is deleted, expanding the blast radius beyond what the annotations state. It does not cover cascading effects on related test runs, steps, or executions, nor permission requirements.

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?

One sentence, zero filler, with the destructive nature and the surprising Jira-issue side effect front-loaded. Every clause earns its place.

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?

With an output schema present, return values need not be explained, and annotations carry the disposition hints. For a destructive one-parameter tool the description is nearly sufficient, missing only cascade scope and permission/undo context.

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?

Single parameter with 100% schema description coverage, so the schema already documents the accepted key/id formats. The description adds nothing about the 'test' argument, making this a baseline 3 case where structured data does the work.

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 verb (Delete), a precise resource (Test issue), and adds that the underlying Jira issue is removed too. The word 'Test' distinguishes it from sibling deletions like xray_delete_test_set, xray_delete_test_plan, and xray_delete_test_execution, though it never explicitly names those alternatives.

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 versus the other delete tools or the alternative update/archive paths, and no stated prerequisites. 'Permanently' hints at caution but is not framed as a when-to-use condition.

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