merge_pull_request

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It simply says 'Merge a pull request' with no information about permissions required, branch deletion behavior, merge conflict handling, or side effects. The mutating nature is implicit but lacks depth.

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 concise single sentence that clearly states the core purpose. It is front-loaded and contains no filler, though it could be slightly expanded to add useful context without becoming verbose.

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?

No output schema, no annotations, and a very sparse description. For a mutation tool with 6 parameters, the description does not cover return values, side effects, or operational context. It is far from complete for an agent to use it confidently.

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 17% (only merge_method is described). The description adds no information about owner, repo, pull_number, commit_title, or commit_message. With most parameters undocumented and no compensation from the description, this is severely lacking.

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 'Merge' on a specific resource 'pull request in a repository'. It distinguishes from siblings like create_pull_request and update_pull_request by specifying the merge operation.

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 (e.g., PR must be open and mergeable) or conditions for successful merging, nor does it differentiate from other PR-related tools beyond the verb 'merge'.

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