Manage pull request reviewer

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

With no annotations provided, the description must carry the behavioral disclosure burden. It only states 'Add or remove,' implying a mutation, but does not disclose the confirmation requirement (confirm parameter must be true), potential side effects, permission requirements, or reversibility. This is a significant gap for a mutation tool.

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, efficient sentence that front-loads the primary action and resource. It has no fluff or redundant content. However, it is perhaps too concise, sacrificing explanatory value for brevity.

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 7 parameters (5 required) and no output schema, the description is inadequate. It does not explain the confirmation mechanism, the meaning of isRequired, the role of project, or any return/result information. An agent would have to infer most behavior from the schema alone, which is sparse.

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 only 14% (only 'confirm' has a schema description). The description mentions 'by Azure DevOps identity ID,' which loosely maps to reviewerId, but it fails to explain other critical parameters such as repositoryId, pullRequestId, action (beyond add/remove), confirm (safety flag), isRequired, or project. The description does not compensate for the low schema coverage.

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 (add or remove) and the resource (PR reviewer) with a specific identifier (Azure DevOps identity ID). It is distinguishable from sibling tools like get_pull_request_reviewers (read-only) and set_pull_request_vote (different action). However, it does not explicitly differentiate from other mutation tools like manage_pull_request_label, though the resource is clear.

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 on when to use this tool versus alternatives. It does not mention prerequisites, such as needing to fetch existing reviewers first, or scenarios where adding/removing a reviewer is appropriate. The description offers no exclusions or references to sibling tools.

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