wit_work_items_link

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'link work items together in batch' implies a write operation, it doesn't disclose important behavioral traits like whether this requires specific permissions, whether links are reversible, what happens on partial failures in batch operations, rate limits, or what the response format looks like. The description is insufficient for a mutation tool with zero annotation coverage.

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 extremely concise at just 6 words, with zero wasted language. It's front-loaded with the core action and immediately specifies the batch scope. Every word earns its place in this minimal but complete statement of function.

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 batch mutation tool with no annotations, no output schema, and incomplete parameter documentation, the description is inadequate. It should explain more about the batch operation behavior, error handling, permissions required, and what constitutes a successful response. The current description leaves too many operational questions unanswered for a tool that modifies data.

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 50%, with the 'project' parameter well-described but the 'updates' array having only partial documentation. The description adds no parameter semantics beyond what's in the schema - it doesn't explain the structure of batch updates, provide examples of valid link types, or clarify how multiple updates are processed. The baseline 3 reflects that the schema does some work but the description doesn't compensate for the coverage gap.

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 ('link work items together') and scope ('in batch'), which provides a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'wit_link_work_item_to_pull_request' or 'wit_work_item_unlink', which would require mentioning the batch nature or specific linking context.

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 provides no guidance on when to use this tool versus alternatives. It doesn't mention prerequisites like required permissions, when batch linking is appropriate versus single operations, or how it differs from related sibling tools such as 'wit_link_work_item_to_pull_request' or 'wit_work_item_unlink'.

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