approve_pull_request

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

For a mutation tool with no annotations, the description should disclose side effects (e.g., notifications, state changes, blocking merges) and required permissions. It only states the action and user context, missing critical 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?

The description is concise (one sentence plus a list of args) and the action statement is front-loaded. However, it could include more useful information (e.g., behavioral context) without becoming overly long.

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 the tool's simplicity (3 required parameters, no enums, output schema exists), the description should cover purpose, usage, and behavior. It fails on usage guidelines and behavioral transparency, making it incomplete for an agent to correctly invoke the tool.

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. The parameter explanations ('The project key.', etc.) are minimal and essentially duplicate the property titles without adding value. They do not explain how to obtain these values or any constraints.

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 first sentence clearly states the action ('Approve') and resource ('a pull request'), and specifies it is as the authenticated user. While there are many sibling pull request tools, the verb 'approve' distinguishes this tool from others like 'decline_pull_request' or 'request_changes_pull_request'. However, there is no explicit differentiation from siblings.

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 other pull request actions, nor any prerequisites (e.g., user must be a reviewer, pull request must not be already approved). No alternatives or when-not-to-use instructions are given.

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