Merge pull request

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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered. The description adds genuine context beyond that: it refuses cleanly when the PR is closed or conflicting, costs 2-3 API calls, is not batch-safe, and lists the output fields. It does not, however, spell out permission/auth requirements for the merge itself.

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 compact and front-loaded: purpose first, then labeled Use/Avoid/Speed/Output/Batch-safe lines. Every line carries selection-relevant information with no filler.

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 an 8-param mutation tool with no output schema, the description supplies the output field list, failure behavior (refusal on closed/conflicting PRs), cost estimate, and routing to project_ci_status. Nothing an agent needs to invoke it correctly is missing.

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 baseline is 3, and the description adds some value by calling out method=squash for a single commit and that delete_branch only applies to same-repo branches. It does not elaborate on repo/provider resolution or commit_title/commit_message, which stay schema-only.

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?

States a specific verb (merge) plus the resource (pull request) and enumerates the three strategies plus the optional branch deletion. It is immediately distinguishable from siblings like project_pr_close, project_pr_comment, and project_pr_create.

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?

Has explicit 'Use when' (CI green, user asked to land the PR) and 'Avoid when' (checks still running — do project_ci_status first; user only wants a review comment) clauses that name the alternative tool. It also recommends method=squash for a single commit, giving concrete selection guidance.

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