merge_pull_request

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

With no annotations, the description carries the full burden. It discloses that merge, squash, and rebase are supported, but fails to mention side effects (e.g., branch deletion), prerequisites (e.g., mergeable state, required reviews), or failure modes. This is comparable to a tool that lists updatable fields without deeper 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 very concise, with two short sentences and no filler. The second sentence is somewhat redundant with the schema enum but still aids quick comprehension, so it earns a strong score without being perfect.

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 mutation tool with no annotations and no output schema, the description is incomplete. It does not explain what the tool returns, what conditions must be met for merging, or any behavioral side effects, leaving an agent without sufficient context to invoke it correctly.

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 baseline is 3. The description adds no additional meaning beyond what the schema already provides for parameters; it merely echoes the merge_method enum values without extra detail.

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 merges a pull request, with a specific verb and resource. It also mentions supported merge methods (merge, squash, rebase), distinguishing it from siblings like close_pull_request or create_pull_request.

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 implies usage for merging pull requests but provides no explicit context for when to use it versus alternatives, nor any exclusion criteria. The purpose is evident from the name, but there is no guidance beyond that.

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