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 of behavioral disclosure. It describes what the tool does but lacks details on permissions required, rate limits, error handling, or response format (e.g., whether it returns plain text, markdown, or structured data). This is a significant gap for a tool with no 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 a single, efficient sentence that front-loads the core purpose ('Get the raw markdown/text content of a wiki page') and adds clarifying scope ('without metadata') without any wasted words. Every part of the sentence contributes essential 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?

Given no annotations and no output schema, the description is minimally adequate for a read-only tool but lacks completeness. It explains what the tool does but omits behavioral details (e.g., permissions, errors) and output specifics, which are crucial for an AI agent to use it correctly in context with sibling tools.

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 input schema already documents both parameters ('wikiIdentifier' and 'path') with descriptions. The description does not add any additional meaning or examples beyond what the schema provides, such as clarifying the format of 'wikiIdentifier' or typical 'path' values, but it doesn't need to since the schema is comprehensive.

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 ('Get'), resource ('raw markdown/text content of a wiki page'), and scope ('without metadata'), distinguishing it from sibling tools like 'get_wiki_page' (which likely includes metadata) and 'list_wiki_pages' (which lists pages rather than fetching content).

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 context by specifying 'raw markdown/text content' and 'without metadata', suggesting it's for extracting content only. However, it does not explicitly state when to use this tool versus alternatives like 'get_wiki_page' or 'get_wiki_page_revisions', nor does it mention any exclusions or prerequisites.

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