ado_work_item_comments_list

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

No annotations are provided, so the description carries the full behavioral disclosure burden. 'List' suggests a read-only operation, but the description does not disclose pagination behavior, ordering, limits, authentication requirements, or any response quirks. The 'top' parameter is behaviorally important but unaddressed.

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 clear sentence with no filler or repetition. Every word contributes meaning, and it is appropriately short for a simple list operation.

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 three parameters, no annotations, and no behavioral guidance, the descrition is incomplete. It does not explain how top and project affect results, whether project is required, or what the response shape contains. The existence of an output schema helps but is not enough to cover the missing pagination and scoping semantics.

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 0% and the description mentions none of the three parameters. While parameter names like work_item_id and top are somewhat self-explanatory, the description does not clarify how 'project' scopes the call or how 'top' limits the returned comments. The description must compensate for the missing schema descriptions but does not.

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 states a specific verb ('List') and resource ('comments') scoped to 'a work item'. This clearly distinguishes it from sibling tools like ado_work_item_comment_add (adds comments) and the pull-request list tools.

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?

There is no guidance about when to use this tool versus alternatives. It does not mention when this should be preferred over ado_work_item_get or how it relates to ado_work_item_comment_add. Usage is only implied by the verb and noun.

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