Github Merge Pr

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

Annotations already establish readOnly=false and destructive=false; the description only restates the action and adds no side effects such as branch cleanup, CI triggers, or required permissions. It does not contradict the annotations.

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?

Two short sentences with no filler. The action is front-loaded and the skill pointer is a compact way to route the agent to conventions.

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?

With six parameters, no param descriptions, and a mutating operation, the description is thin; however, the workflow pointer and existing output schema/annotations mitigate the gap. It leaves behavioral and parameter details to be fetched from the skill.

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% and the description does not explain merge_method, commit_title, commit_message, or repo fields. It only adds 'specific' to indicate pr_number selection, which leaves most parameter meaning to inference.

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 states a specific verb ('Merges') and resource ('a specific pull request'), and no sibling tool claims the merge operation, so the agent can immediately distinguish it from create/update PR tools.

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?

It provides a workflow pointer to github_get_skill('pr-management'), which implies the correct usage context, but it does not say when to use this tool instead of update_pr or other PR tools.

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