create_work_item_link

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

Annotations indicate readOnly=false and destructive=false, which aligns with the 'Add' action. However, the description adds no behavioral context beyond the annotations, such as whether this creates an external URL link, how project_id/work_item_id are used, or what response to expect.

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 a single, front-loaded sentence with no filler, which is structurally concise. However, it is too sparse to be genuinely useful for a tool with six parameters and ambiguous behavior, so it does not fully earn its place.

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?

With six parameters, no output schema, and minimal annotation help, this one-sentence description is grossly insufficient. It does not cover prerequisites, return values, the meaning of external link fields, or how this tool differs from relation-based tools.

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 only 17%, with only 'url' described in the schema. The description itself does not explain project_id, work_item_id, external_id, external_source, or title, leaving nearly all parameters semantically opaque.

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 'Add' with resource 'link to a work item', clearly distinguishing it from create_work_item and link-related sibling tools like update_work_item_link. However, it lacks an explicit scope or alternative tool references, so it falls short of a top score.

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 gives no guidance on when to use this tool versus alternatives such as create_work_item_relation or update_work_item_link. It simply states the action without any context, exclusions, or prerequisites.

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