contentrain_merge

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

The description fully details the tool's behavior: merging, advancing base branch via update-ref, selective file sync, and branch pruning. This goes beyond the annotation flags (readOnlyHint: false, destructiveHint: false) by explaining the operations, ensuring the agent understands the actions it will perform.

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 three sentences long, front-loading the core purpose and then adding details. Every sentence contributes essential information with no fluff. It is appropriately sized for the tool's complexity.

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?

The description covers the main functionality but lacks details on what happens on failure, prerequisites (e.g., repository state), or return format. Given no output schema, more context on error handling or status would improve completeness for a complex merge operation.

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 100% schema description coverage, the baseline is 3. The description adds value by explaining the targeting logic (exact branch vs. model/locale resolution), which is not fully captured in the individual parameter descriptions. This helps the agent understand how to combine parameters.

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 that the tool merges a review-mode branch into contentrain, specifying it's a local git operation. It lists distinct actions (advance base, sync files, prune branch), making the purpose specific and distinguishable from sibling 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?

The description explains how to target the branch (by exact name or by model/locale/latest) but does not provide guidance on when to use this tool versus alternatives like contentrain_apply or contentrain_branch_delete. No explicit when-to-use or when-not-to-use context.

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