uvcs_merge_confirm

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

Adds substantial context beyond the destructive/readOnly annotations: refusal conditions (pending changes, conflicts), the fact that the merge result stays pending until a checkin, the prepare/confirm workflow, and the human-approval requirement. These are exactly the operational traits an agent needs before a destructive mutation.

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?

Front-loads the merge action and refusal conditions well, but the closing sentences are partly redundant ('Requires prepare/confirm' then 'Confirms and executes a prepared operation'), costing a little efficiency.

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, non-idempotent mutation with no output schema, the description covers prerequisites, refusal states, and approval gating. It only omits what the confirmation returns, which is minor.

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 coverage is 100%, so token and confirmPhrase are already documented in the schema (including the exact phrase requirement). The description references the prepare/confirm pairing but adds no syntax or format detail beyond the schema, so the baseline 3 applies.

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?

States a specific verb (merge) and resource (branch/changeset/label into the current workspace branch), then clarifies it confirms and executes a prepared operation. An agent can distinguish it from uvcs_merge_prepare and uvcs_merge_preview without opening any schema.

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?

Explicitly gates invocation: 'Call only after the user has reviewed the prepared payload and explicitly approved this exact operation,' plus the prerequisite of prepare/confirm. It also names when-not (refused on tracked pending changes or conflicts) and routes conflict resolution to the UVCS client.

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