Azure DevOps MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Switch to' implies a state change operation, it doesn't disclose important behavioral aspects like whether this requires specific permissions, whether the change is persistent across sessions, what happens to ongoing work, or what the expected response looks like. For a tool that changes context with no 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 perfectly concise with two sentences that each serve a clear purpose: the first states what the tool does, and the second provides usage guidance. There's zero wasted language, and the information is front-loaded with the core purpose stated first.

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 tool with one parameter (100% schema coverage) but no annotations and no output schema, the description provides adequate but incomplete context. It explains the purpose and gives a prerequisite, but doesn't address behavioral aspects like what 'switching' entails operationally, what permissions are required, or what happens after the switch. The lack of output schema means the description should ideally mention what to expect as a result.

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%, so the schema already documents the single 'project' parameter with its type and purpose. The description doesn't add any additional parameter semantics beyond what's in the schema, such as format requirements, validation rules, or examples of valid project names. The baseline of 3 is appropriate when 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 action ('Switch to') and resource ('a different project within the current organization'), making the purpose immediately understandable. It doesn't explicitly differentiate from siblings like 'get_project', but the verb 'Switch to' implies a state change operation rather than a retrieval, which provides some 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 provides clear contextual guidance by stating 'Use list_projects first to see available projects', which gives a prerequisite action. However, it doesn't explicitly state when NOT to use this tool or mention alternatives among the many sibling tools, which would be needed for a perfect score.

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