Azure DevOps MCP Server

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states the action without any details on permissions, rate limits, pagination, error handling, or return format. For a tool that likely queries a work item hierarchy, this omission is significant and leaves the agent unprepared for invocation.

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 no wasted words. It's front-loaded and appropriately sized for the minimal content it conveys, though its brevity contributes to the lack of detail in other dimensions.

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 work item hierarchies, no annotations, no output schema, and 0% schema description coverage, the description is incomplete. It doesn't address return values, error cases, or how child work items are structured, making it inadequate for effective tool 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 input schema has 1 parameter with 0% description coverage, and the tool description adds no meaning beyond the schema. It doesn't explain what 'parentId' represents (e.g., a work item ID), its format, or constraints. With low schema coverage, the description fails to compensate, leaving the parameter undocumented.

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 child work items of a parent' restates the tool name 'get_child_work_items' without adding specificity. It mentions the resource ('child work items') and target ('parent'), but lacks a clear verb beyond 'get' and doesn't differentiate from sibling tools like 'get_work_item_parent' or 'get_work_items_by_ids'. This is a tautology that provides minimal additional insight.

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. With siblings like 'get_work_item_parent' (which retrieves a parent of a work item) and 'get_work_items_by_ids' (which retrieves multiple work items by ID), the description offers no context for selection, prerequisites, or exclusions, leaving the agent to guess based on the name alone.

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