manage_review

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

Annotations are all false, providing no hints about mutability or destructiveness. The description discloses basic behavioral traits (each action's effect) but does not cover permissions, side effects, or what happens after actions (e.g., whether approval triggers anything). Adequate but not exhaustive.

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 three short sentences, front-loaded with the overall purpose, then specifying actions. No redundant text; every sentence is essential.

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?

Given 6 parameters (3 required, 2 enums) and no output schema, the description covers core functionality and action-specific parameters. It could mention defaults (e.g., project) or error behavior, but it is largely complete for typical usage.

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 coverage is 100%, so parameters are documented. The description adds value by linking 'commentText' and 'participantStatus' to the 'publish' action, clarifying their usage beyond the schema's descriptions.

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 tool's purpose: 'Approve, unapprove, or publish a review on a pull request.' It uses a specific verb ('manage' implied) and distinguishes from sibling tools by focusing on review actions on pull requests.

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 explicit usage for each action: 'Use "approve" to approve, "unapprove" to remove your approval, and "publish" to submit a review with an optional overview comment and status.' While it does not explicitly compare to alternatives (e.g., manage_comment or merge_pull_request), the guidance is clear for the intended use.

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