jira_link_remove

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

With no annotations, the description fully covers destructive nature, explicit confirm guard, dry_run behavior, return format (YAML {status: ok}), and CLI mirror. No hidden surprises.

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?

Packed with valuable info in two sentences, slightly lengthy but efficient and front-loaded.

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?

Despite no output schema, description explains return format and covers all required behavior. Complete for a destructive tool with guard and dry-run.

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 description adds critical context: link_id source, confirm as destructive guard, dry_run previews request without confirm. Exceeds baseline 3.

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 uses a specific verb (Remove) and resource (JIRA issue link by its link ID), and distinguishes from siblings like jira_link_list and jira_read for discovering IDs.

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?

Explicitly tells when to use jira_link_list or jira_read to discover IDs, and explains the destructive nature requiring confirm and dry_run usage. Does not explicitly list when not to use, but context implies it.

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