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 states the tool lists work items with filters, implying a read-only operation, but doesn't cover critical aspects like pagination (e.g., the 'top' parameter's default of 50), rate limits, authentication needs, error handling, or return format. For a tool with 6 parameters and no output schema, this is a significant gap in transparency.

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: 'List work items by type (Epic, Feature, User Story, Task, Bug) with filters.' It is front-loaded with the core action and includes key details without redundancy. Every word earns its place, making it highly concise and well-structured.

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 (6 parameters, no annotations, no output schema), the description is insufficient. It lacks details on behavioral traits (e.g., pagination, errors), output format, and usage context compared to siblings. While concise, it doesn't compensate for the missing structured data, leaving gaps for an agent to invoke the tool effectively.

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 all parameters (e.g., 'type' as 'Work item type,' 'top' with default 50). The description adds minimal value by mentioning 'by type...with filters,' which aligns with the schema but doesn't provide additional semantics like format examples or constraints. 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: 'List work items by type (Epic, Feature, User Story, Task, Bug) with filters.' It specifies the verb ('List'), resource ('work items'), and scope ('by type...with filters'), making the function unambiguous. However, it doesn't explicitly differentiate from sibling tools like 'get_work_items_by_ids' or 'query_work_items,' which prevents 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 mentions filtering but doesn't compare to sibling tools like 'search_work_items' or 'query_work_items,' nor does it specify prerequisites or exclusions. This lack of contextual direction leaves the agent to infer usage from the tool name alone.

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