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 the full burden of behavioral disclosure but only states the basic action. It doesn't cover critical aspects like authentication requirements, rate limits, error handling, or what the output looks like (e.g., JSON structure). 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 extremely concise with just three words, making it front-loaded and efficient. However, it borders on under-specification, as more detail could improve clarity without sacrificing brevity. It earns a 4 for zero waste but loses a point for potential oversimplification.

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 complexity of a pull request tool with 5 parameters and no output schema, the description is incomplete. It lacks information on return values, error conditions, and behavioral traits like pagination or data formats. With no annotations to supplement, this leaves the agent with insufficient context for reliable 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?

The schema description coverage is 100%, with clear documentation for all 5 parameters in the input schema. The description adds no additional meaning beyond the schema, such as explaining relationships between parameters or usage examples. Baseline score of 3 is appropriate since the schema adequately covers parameter semantics.

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 'Get pull request details' states the basic verb+resource but is vague about scope and depth. It doesn't specify what details are included by default versus what requires optional parameters, nor does it distinguish itself from sibling tools like 'get_pr_comments' or 'list_pull_requests' which might overlap in functionality.

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?

No guidance is provided on when to use this tool versus alternatives. The description doesn't mention sibling tools like 'get_pr_comments' for comments or 'list_pull_requests' for listings, nor does it specify prerequisites such as authentication or project context. Usage is implied but not explicitly defined.

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