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

Annotations already cover safety (readOnlyHint=false, destructiveHint=true, idempotentHint=true), so the bar is lower; the description still adds real behavioral context by disclosing that clearing happens via an empty string and that every linked id must belong to the same organization. It does not say whether clearing is reversible or whether linking replaces existing links.

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?

Three short sentences, front-loaded with purpose before the set/clear mechanics and the org constraint. No filler or redundancy.

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?

There is no output schema, so the description must carry the read-side burden, and it adequately explains the three link axes, the set/clear protocol, and the org constraint. Minor gaps remain around error behavior and whether linking overwrites prior values, but nothing essential for correct invocation is missing.

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 75% and each optional param already documents 'or empty string to unlink', so the baseline is 3. The description adds value on top by stating the set/clear convention globally and imposing the same-organization constraint on every id, which the schema omits.

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 states a precise verb (Attach/clear) and resource (cross-artifact links on an Issue) and enumerates the exact link kinds: fix-Task, source ProjectRisk, ChangeRequest. That enumeration separates it from generic siblings such as update_issue, attach_link, and link_dependency without needing to open any schema.

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?

It gives clear operational guidance for setting versus clearing ('Pass the id to set, or an empty string to clear that link'). However, it names no alternative tool or exclusion, so an agent still has to infer when link_issue is preferable to update_issue or create_issue.

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