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 mentions the tool returns 'matching files with line context,' which gives some output behavior, but lacks critical details like whether it's read-only (implied but not stated), pagination handling, rate limits, authentication requirements, or error conditions. For a search tool with zero annotation coverage, this is insufficient.

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—two sentences that efficiently convey the core functionality and output. It's front-loaded with the main purpose and wastes no words, making it easy for an agent 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 the tool's moderate complexity (search with filtering), lack of annotations, and no output schema, the description is minimally adequate. It covers what the tool does and the output format but misses behavioral details (e.g., performance, limits) and usage context. With no output schema, it should ideally describe return structure more, but the 'line context' hint provides some value.

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 fully documents all four parameters (searchText, top, repository, branch). The description adds no additional parameter semantics beyond what's in the schema—it doesn't clarify regex syntax, default values beyond 'top', or interactions between parameters. 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 tool's purpose: 'Search for code across all repositories in the project. Returns matching files with line context.' It specifies the verb ('search'), resource ('code'), scope ('across all repositories'), and output format. However, it doesn't explicitly differentiate from sibling tools like 'search_work_items' or 'list_repositories', which would be needed for 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 doesn't mention sibling tools like 'search_work_items' (for non-code searches) or 'list_repositories' (for repository listings), nor does it specify prerequisites, exclusions, or contextual triggers for choosing this tool over others.

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