git_branch_merge

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

There are no annotations, so the description must carry the full burden of behavioral disclosure. 'Merge a branch into current' describes the action but does not mention potential side effects such as creating a merge commit, modifying the working tree, or failing due to conflicts. It adds minimal value beyond the tool name.

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 that is front-loaded and easy to read. While it is terse, it contains no filler and is appropriately sized for a simple tool, though it could include more context without becoming verbose.

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 that this is a mutation tool with no annotations, no output schema, and an undocumented parameter, the description is notably incomplete. It does not explain the result of the operation, error behavior, or any side effects, making it insufficient for an agent to fully anticipate outcomes.

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?

With 0% schema description coverage and only one parameter ('branch'), the description does not explicitly explain the parameter's meaning or format. The phrase 'a branch' hints that 'branch' is the source branch, but it lacks explicit definition.

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 'Merge a branch into current' clearly identifies the action (merging), the object (a branch), and the target (the current branch). It distinguishes this tool from siblings like git_branch_create, git_branch_delete, and gh_pr_merge.

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 is provided on when to use this tool versus alternatives. It does not mention prerequisites (e.g., clean working tree), when not to use it, or compare with related operations like git_pull or gh_pr_merge.

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