ado_pull_requests_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. It only states a basic list operation and says nothing about whether the call is read-only, whether results are paginated, how the 'top' limit behaves, or what happens when neither project nor repository is provided. The agent is left without important behavioral context.

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?

A single sentence that states the verb, resource, and scope with no filler. The core action is front-loaded, and every word contributes to the meaning. It is appropriately concise for a 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?

The description is adequate for a straightforward list tool but leaves important gaps: whether project and repository are mutually exclusive or cumulative, what defaults apply, and how the results are limited. The presence of an output schema partially compensates, but given zero annotations and zero parameter descriptions, more detail is needed for fully confident invocation.

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 adds some meaning for 'project' and 'repository' by framing them as scoping filters, but it does not explain the 'top' parameter, the relationship between the filters (e.g., can both be used together), or what default null values imply. This is insufficient for full parameter understanding.

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 the specific verb 'List' with the resource 'pull requests' and adds a scoping phrase 'in a project or repository'. This clearly communicates the core operation and distinguishes it from sibling tools like ado_pull_request_get (fetch a single PR) and ado_pull_request_create. It does not explicitly name a sibling, but the operation is unambiguous.

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 does not mention that this is the listing entry point, when to prefer ado_pull_request_get for a single PR, or how the optional project/repository filters interact. Usage is only implied by the verb 'List'.

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