delete_work_item_link

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the description does not need to repeat the safety profile. However, it adds no extra behavioral context such as irreversibility, whether the linked item is also deleted, or permission requirements. It is not misleading and is consistent with the annotations, meriting a baseline score.

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, concise sentence that immediately states the operation. It is front-loaded and every word earns its place. No filler or redundant phrasing is present.

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?

Despite having annotations, the description is too terse for a destructive operation. There is no output schema and no explanation of the difference between links and relations, return values, error handling, or prerequisites. The agent is left without enough context to use the tool confidently in a real workflow.

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% and the description provides no explanation of the parameters. While the names (project_id, work_item_id, link_id) are self-explanatory, there is no clarification of what a 'link' is, how link_id relates to the work item, or how to obtain these identifiers. The description completely fails to compensate for the lack of schema details.

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 the action ('Delete') and the target resource ('a link from a work item'). It is specific enough to distinguish from sibling tools like create_work_item_link, update_work_item_link, or retrieve_work_item_link, which share the same resource but different operations.

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 provided on when to use this tool versus alternatives such as remove_work_item_relation. The description does not mention prerequisites, typical scenarios, or cases where this tool should not be used, leaving the agent to infer from the tool name alone.

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