jira_remove_issue_link

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

The description discloses that the tool modifies data (deletes a link) and raises errors for missing link_id, read-only mode, or client unavailability. This adds context beyond what annotations might provide (none provided).

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 each sentence providing necessary information. The Args/Returns format adds structure but could be slightly shorter.

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?

The description covers the action, parameter, return type, and error conditions. With an output schema present, this is sufficient for a simple delete-link tool.

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?

Parameter link_id has full schema coverage with description. The tool description repeats the same info and adds minimal extra meaning. Baseline 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 'Remove a link between two Jira issues,' specifying the action and resource. It is distinct from sibling tools like jira_create_issue_link or jira_delete_issue.

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 explicit guidance on when to use this tool versus alternatives, but the purpose is obvious. Missing mention of prerequisites such as needing a valid link_id.

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