MCP Server for Azure DevOps

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Create a new work item' implies a write/mutation operation, but the description doesn't address important behavioral aspects: what permissions are required, whether the creation is immediate or queued, what happens on failure, whether there are rate limits, or what the response contains. For a mutation tool with zero annotation coverage, this is a significant gap.

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 4 words, front-loading the essential action and resource. There's zero wasted language or redundancy. While it may be too brief for complete understanding, it achieves maximum efficiency in its current form.

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 5 parameters, no annotations, and no output schema, the description is insufficiently complete. It doesn't address the behavioral implications of creation, doesn't explain the resource context (what a 'work item' represents in this system), and provides no guidance on usage. The combination of being a write operation with multiple parameters and no structured safety information requires more descriptive context than provided.

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 100%, so the schema already documents all 5 parameters thoroughly. The description adds no additional parameter information beyond what's in the schema - it doesn't explain relationships between parameters, provide examples of valid values, or clarify the 'fields' object structure. With complete schema coverage, the baseline score of 3 is appropriate as the description doesn't add value but doesn't need to compensate for gaps.

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 verb ('Create') and resource ('work item'), making the purpose immediately understandable. It distinguishes from sibling tools like 'get_work_item', 'update_work_item', and 'query_work_items' by focusing on creation rather than retrieval or modification. However, it doesn't specify what a 'work item' is in this context, leaving some ambiguity about the resource being created.

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. With multiple sibling tools like 'update_work_item' and 'query_work_items', there's no indication of when creation is appropriate versus updating existing items or querying for items. No prerequisites, dependencies, or typical use cases are mentioned.

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