Request pull request changes

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

With no annotations, the description carries the behavioral disclosure burden and does so well: it identifies the mutation, the exact resulting vote value, and the required safeguards (write tools and confirm=true). It does not mention reversibility or response details, but the core safety-relevant behavior is clear and not contradicted by any annotation.

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 sentences efficiently front-load the primary behavior and then state prerequisites. There is no filler or redundant explanation; every phrase earns its place.

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 covers the essential mutation behavior, permission requirement, and confirmation guard, which is strong for a simple tool. However, it omits how this relates to set_pull_request_vote and gives no return or post-invocation context, which leaves an agent with incomplete information when selecting among related vote tools.

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 100%, so the parameters are already documented. The description repeats the confirm requirement but adds no new parameter semantics beyond what the input schema provides. Baseline 3 is appropriate.

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 clearly states the action: it sets the authenticated user's Azure DevOps vote to waitForAuthor (-5), which is a specific verb, resource, and outcome. It is clearer than a generic 'request changes' but it does not explicitly differentiate itself from sibling set_pull_request_vote, which may overlap in capability.

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 such as set_pull_request_vote. 'Requires write tools and confirm=true' is a prerequisite, not a usage context or exclusion. An agent receives no help selecting between closely related pull-request voting tools.

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