ado_pull_requests_list

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered; the description adds the useful "bounded page" behavior. However, it omits the most consequential behavior for an agent: status defaults to "active", so completed and abandoned PRs are silently excluded, and page size is capped at 100.

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?

Two short, front-loaded sentences with no filler. It is efficient, though the second sentence spends its budget on pagination while more important semantics are left out.

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?

With four parameters, a nested required target object, 0% schema coverage, no output schema, and no annotations covering filtering behavior, the definition is too thin. An agent cannot tell what scope of PRs it will get back or how to shape the target object from this description alone.

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 carries full burden, yet it explains only skip. The required nested target object (organization/project/repository/repoPath/profile) and the status enum with its non-obvious "active" default go entirely unmentioned.

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 gives a specific verb and resource ("List ... repository pull requests") and distinguishes it from ado_pull_request_get by framing it as a paged listing. It does not explicitly name the sibling, but "list a bounded page" is unambiguous against the singular get tool.

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?

"Use skip to page" is the only usage instruction, and it addresses just one of four parameters. There is no guidance on when to pass a status filter, when to use this versus ado_pull_request_get, or that the default result set is limited rather than comprehensive.

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