execute_merge

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

The description adds the behavioral detail that the tool updates the 'work_branches' table on success, which goes beyond annotations. Annotations already mark the tool as destructive (destructiveHint=true). The description does not elaborate on failure behavior, side effects on the repository, or permissions required, but it provides some additional context.

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 extremely concise—two short sentences that efficiently convey the primary action and a key side effect. No unnecessary words or repetition; every sentence earns its place.

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?

Despite being concise, the description lacks important context. It does not specify the target branch (presumably the current branch), how conflicts are handled, whether the merge is committed automatically, or what the 'result' contains. For a destructive merge tool with no output schema, more detail is needed for safe and correct usage.

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?

The input schema has 100% coverage: source_branch is described as 'Branch to merge from'. The description does not add any further meaning beyond what the schema provides. With full schema coverage, the baseline of 3 is appropriate.

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 clearly states the tool executes a git merge and returns a result. It specifies the action and the resource (git merge), making the purpose clear. However, it does not differentiate from siblings like 'detect_conflicts_before_merge' which is a related but distinct action.

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 usage guidance is provided. The description does not indicate when to use this tool versus alternatives (e.g., detect_conflicts_before_merge for pre-checking, or sync_git_state for syncing state). There is no mention of prerequisites, such as being on the target branch or having no existing conflicts.

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