delete_work_item_link

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

With no annotations provided, the description carries the full burden of behavioral disclosure, but it only restates the obvious 'Delete' action. It omits irreversibility, permission requirements, side effects on related data, and error behavior, which is a significant gap for a destructive operation.

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 compact and front-loaded: a one-line purpose statement followed by a clean Args block. Every line earns its place, with no redundant prose, though the brevity leaves behavioral details unaddressed.

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?

For a simple three-parameter delete tool, the description covers the essential operation and parameter meanings. However, it lacks any behavioral context such as side effects, success/error responses, permission needs, and it never distinguishes links from the closely related 'relations' concept, making it only minimally viable.

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 0%, so the Args block adds meaningful value by explaining each parameter's semantic role (UUID of project, work item, and link). This compensates for the bare string-only schema, though it stays minimal and does not add constraints or relationships beyond the basics.

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 'Delete a link for a work item' specifies a clear verb (Delete) and resource (link for a work item), making the operation unambiguous. It distinguishes this tool from siblings such as create_work_item_link, update_work_item_link, and remove_work_item_relation by naming the link as the target.

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 guidance is given on when to use this tool versus alternatives like remove_work_item_relation or delete_work_item_attachment. There are no prerequisites, exclusions, or contextual hints beyond what the tool name already implies.

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