Azure DevOps MCP Server

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

No annotations are provided, so the description carries full burden. It mentions execution and returning results, but lacks details on permissions needed, rate limits, pagination behavior, error conditions, or whether this is a read-only operation. For a tool that executes queries and returns work items, this leaves significant behavioral gaps.

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, efficient sentence that clearly states the tool's purpose without unnecessary words. It's front-loaded with the core action and result, making it easy to parse quickly.

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?

Given no annotations and no output schema, the description is minimally adequate for a simple execution tool with one parameter. However, it doesn't address important context like what format the work items are returned in, whether this is a read-only operation, or any performance considerations. The schema covers the parameter well, but overall completeness is limited.

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 the single parameter 'queryId' with its description. The description doesn't add any additional parameter semantics beyond what's in the schema, such as format examples or validation rules. Baseline 3 is appropriate when schema does the heavy lifting.

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 ('execute') and resource ('saved work item query'), and specifies the outcome ('return the matching work items'). It distinguishes from siblings like 'list_saved_queries' (which lists queries) and 'query_work_items' (which runs ad-hoc queries), but could be more explicit about this distinction.

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 implies usage when you have a saved query ID and want to execute it, but doesn't explicitly state when to use this vs. alternatives like 'query_work_items' for ad-hoc queries or 'list_work_items' for unfiltered lists. The input schema hints at getting the queryId from 'list_saved_queries', providing some contextual guidance.

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