Github Merge Pr

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true. The description adds no behavioral context beyond 'merges', which is already implied by the name. It doesn't disclose side effects like closing the PR, creating a merge commit, or triggering deployments. However, since annotations cover the safety profile (not read-only, not idempotent, not destructive), the description doesn't contradict them and adds minimal value. A 3 is appropriate because the description is consistent but doesn't enrich the annotation-provided behavior.

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 single concise sentence with no wasted words. It is front-loaded with the action. However, it is so brief that it misses opportunities to add value, but for what it contains, it is efficient.

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 has 6 parameters, 0% schema description coverage, and an output schema, the description is too thin. It doesn't explain the merge method options, the effect of commit_title/commit_message, or any preconditions. The output schema exists but the description doesn't clarify what the response represents (e.g., merged PR details). For a mutation tool with no parameter documentation, this is inadequate.

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 for parameter meaning. It does not. The description only mentions 'a specific pull request' but doesn't explain that repo_owner, repo_name, and pr_number identify the target, nor does it clarify merge_method options (merge/squash/rebase) or commit_title/commit_message overrides. The enum for merge_method is self-explanatory, but the optional parameters' semantics are left entirely to the schema, which lacks descriptions.

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 'Merges a specific pull request' clearly states the verb (merges) and resource (a specific pull request). It distinguishes from siblings like github_create_pr and github_update_pr, though it doesn't explicitly name them. The title is redundant but the description is clear enough.

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 like github_update_pr_branch or github_submit_review. The description implies usage for merging but doesn't state prerequisites (e.g., PR must be open, mergeable, or have required reviews) or when not to use it. Sibling tools exist for related PR operations, but no routing is provided.

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