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

Annotations already declare destructive=true, readOnly=false and openWorld=true, so the safety profile is covered. The description adds useful context beyond annotations: it changes the target branch, requires an explicit user request, and enforces a confirm:true gate.

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?

It is a short, front-loaded description. The write warning, action, usage constraint, and safety gate all appear immediately with no wasted words.

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 destructive GitHub mutation with full parameter documentation and rich annotations, the description gives everything needed to call it correctly: what it does, when to use it, and the confirm requirement.

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 all six parameters are already documented. The description reinforces the confirm gate and method choices but adds little semantically beyond the 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 names a specific verb and resource (merge a GitHub pull request) and specifies the supported merge strategies, making it clearly distinct from read-only siblings such as github_get_pr and github_list_prs.

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 gives a clear condition for use — only when the user has explicitly asked to merge — and states the confirm gate. It does not name a specific alternative sibling, but no alternative applies for a merge operation.

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