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 the full burden. It mentions the output is a 'table of contents', which hints at a structured list, but fails to disclose critical behavioral traits such as pagination, rate limits, authentication requirements, error conditions, or whether it's a read-only operation. This leaves significant gaps for an agent to understand how to invoke it safely and effectively.

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 with zero waste. It is front-loaded with the core purpose and includes a clarifying parenthetical, making it easy to parse quickly without unnecessary elaboration.

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 the lack of annotations and output schema, the description is incomplete for a tool with 3 parameters. It covers the basic purpose but omits behavioral context (e.g., safety, performance) and output details. However, the high schema coverage for inputs and the clear purpose prevent it from scoring lower, as it meets the minimum viable threshold for a read-oriented tool.

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?

The schema description coverage is 100%, meaning the input schema already documents all parameters thoroughly. The description adds no additional meaning beyond the schema, such as explaining the 'wikiIdentifier' format or clarifying the 'recursionLevel' options. However, with high schema coverage, a baseline score of 3 is appropriate as the 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 ('List') and resource ('all pages in a wiki'), with the parenthetical '(table of contents)' providing additional context about the output structure. However, it does not explicitly differentiate from sibling tools like 'get_wiki_page' or 'list_wikis', which reduces it from a perfect score.

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 does not mention sibling tools like 'get_wiki_page' (for single pages) or 'list_wikis' (for listing wikis themselves), nor does it specify prerequisites or exclusions for usage.

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