MCP Server for Azure DevOps

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

With no annotations provided, the description carries full burden but only states it makes API calls without disclosing behavioral traits like authentication requirements, rate limits, error handling, or response formats. It mentions HTTP methods but doesn't explain implications (e.g., DELETE is destructive). This is inadequate for a generic API tool with mutation capabilities.

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—'Make a generic Azure DevOps REST API call'—that front-loads the core purpose. Every word earns its place, making it appropriately sized for the tool's scope.

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 complexity (generic API caller with 5 params including nested objects, no output schema, and no annotations), the description is incomplete. It lacks details on authentication, error handling, response structure, and when to use versus siblings, making it inadequate for safe and effective agent use.

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 5 parameters. The description adds no additional parameter semantics beyond what's in the schema (e.g., no examples of endpoint paths beyond '/git/repositories', no clarification on params/body usage). Baseline 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 tool's purpose as 'Make a generic Azure DevOps REST API call', which specifies the verb ('Make'), resource ('Azure DevOps REST API call'), and scope ('generic'). It distinguishes from siblings by being a generic API caller versus their specific operations, though it doesn't explicitly name the 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 no guidance on when to use this tool versus the many specialized sibling tools (e.g., create_work_item, get_build). It lacks explicit when/when-not instructions or alternative recommendations, leaving usage context entirely implied from the generic nature.

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