ado_pull_request_threads_list

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

With no annotations, the description carries the full burden of behavioral disclosure. The verb 'List' clearly implies a read-only operation, and 'for a pull request' defines scope. However, it does not mention pagination, ordering, filtering, or whether all thread states are returned, leaving some behavioral ambiguity.

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, tightly worded sentence that immediately communicates the tool's purpose. Every word contributes meaning, and there is no redundant content.

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 simple list operation with an output schema available, the description is minimally adequate: it states the core purpose and implies the key parameter. But it lacks parameter semantics, usage guidelines, and behavioral caveats, leaving clear gaps for an agent attempting to invoke it confidently.

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%, so the description must compensate. It only implies that pull_request_id identifies the PR, but it does not explain repository or project, their relationship, or any constraints on their values. The description adds minimal meaning beyond the raw parameter names.

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 uses a specific verb ('List') and a specific resource ('review threads and comments for a pull request'). It clearly distinguishes this tool from siblings like ado_pull_requests_list (lists PRs) and ado_pull_request_thread_add (adds a thread).

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 about when to use this tool versus alternatives. It does not mention sibling tools, exclusions, or conditions that would route an agent to a different tool such as ado_pull_request_get or ado_pull_request_thread_add.

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