Unlink Issue From Test Case

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

The description states the operation is idempotent, aligning with the idempotentHint annotation. It explains the behavior when the issue is already unlinked (returns successful confirmation). This adds context beyond the annotations without contradicting them.

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 concise with two short paragraphs. The first sentence clearly states the purpose, and the second adds necessary behavioral and parameter context. No superfluous words.

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 tool's simplicity, the presence of an output schema, and the annotations, the description provides sufficient context. It covers idempotency, input format, and result behavior, making it complete for invocation.

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%, but the description adds value by explaining that the issue_id can be either a project key (e.g., PROJ-123) or an internal issue-link ID. This clarifies the parameter's meaning beyond the schema's description.

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 'Unlink an issue from a test case,' which is a specific verb+resource pair. It distinguishes itself from sibling tools like 'link_defect_to_test_case' and other test case management tools.

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 mentions idempotency and the acceptable formats for the issue ID (key or internal ID), providing clear context for usage. However, it does not explicitly state when to use this tool versus alternatives or provide exclusions.

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