Azure DevOps MCP Server with PAT Authentication

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. It correctly indicates this is a write operation ('Add'), but doesn't specify permission requirements, whether links are reversible, rate limits, or what happens on success/failure. The description adds some context about the two linking methods but lacks comprehensive behavioral details for a mutation tool.

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 perfectly concise with two sentences that each earn their place: the first states the purpose and scope, the second explains the two implementation approaches. It's front-loaded with the core functionality and wastes no words on redundant information.

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 mutation tool with 11 parameters, no annotations, and no output schema, the description provides adequate but incomplete context. It covers the what and how but lacks behavioral details (permissions, side effects, error handling) and output expectations. The high schema coverage helps, but the description should do more given the tool's complexity and mutation nature.

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?

With 100% schema description coverage, the schema already documents all 11 parameters thoroughly. The description adds marginal value by mentioning the two linking approaches (full URI vs. components) and listing artifact types, but doesn't provide additional parameter semantics beyond what's already in the schema descriptions. This meets the baseline for high schema coverage.

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 specific action ('Add artifact links') and target resource ('to work items'), distinguishing it from sibling tools like wit_add_child_work_items or wit_add_work_item_comment. It specifies the types of artifacts (repository, branch, commit, builds) and provides two distinct methods for linking (full URI or individual components).

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 clear context about when to use this tool (adding artifact links to work items) and offers guidance on two approaches (full URI vs. component-based). However, it doesn't explicitly state when to choose this tool over alternatives like wit_link_work_item_to_pull_request or wit_work_items_link, nor does it mention prerequisites or exclusions.

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