Add Jira Issue Link

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

Annotations already declare it is a non-read-only, non-idempotent, open-world mutation. The description adds useful behavioral context by explaining outward versus inward verb direction and the returned object shape, though it does not mention duplicate-link behavior or 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?

Two tight sentences with the core action and directional semantics front-loaded. The return-shape sentence is brief and informative without adding clutter.

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 tool is a simple three-parameter mutation, and the description covers the action, parameter directionality, and return shape. With annotations and full schema coverage, it is nearly complete, though it omits edge cases such as duplicate links or invalid link types.

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 description coverage is 100%, so all three parameters are already well documented in the schema. The description reinforces the source/target directionality but adds little syntax or format detail beyond what the schema provides.

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 and resource: "Create a link between two Jira issues." It also clarifies the directionality of the link, which is the key semantic distinction for this operation.

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 implies usage through "Create a link," which distinguishes it from sibling tools like jcm_removeIssueLink and jcm_getIssueLinks. However, it does not explicitly state when to use this tool versus checking existing links or removing links.

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