merge_pull_request

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

No annotations are provided, so the description carries full burden. It states the action is a merge but doesn't disclose critical behavioral traits: whether this is a destructive/write operation (implied but not explicit), permission requirements, rate limits, or what happens on failure. The description lacks behavioral context beyond the basic action.

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?

Well-structured with clear sections (Args, Returns). The first sentence states the purpose directly. Each parameter explanation is brief but informative. No wasted words, though the 'Returns' section is minimal given no output schema.

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 no annotations and no output schema, the description covers parameters well but lacks behavioral context (permissions, side effects, error handling). For a mutation tool with 5 parameters, it's adequate but has clear gaps in completeness regarding how the tool behaves beyond basic parameter semantics.

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. It provides meaningful semantics for all 5 parameters: explains what repo_slug and pr_id are, lists merge_strategy options with default, clarifies close_source_branch behavior, and notes message is optional. This adds substantial value beyond the bare schema.

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 a pull request') and identifies the resource. It's specific about the verb and resource, but doesn't explicitly differentiate from siblings like 'approve_pr' or 'decline_pr' which are related PR operations.

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 on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., PR must be approved), nor does it contrast with sibling tools like 'decline_pr' or 'approve_pr' that might be alternatives in different scenarios.

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