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

Beyond the annotations (destructiveHint=true, idempotentHint=false), the description discloses a concrete failure mode (STALE_TS_REVISION when master changed) and a concurrency constraint ('merges apply one at a time'). That adds real behavioral value the annotations don't carry, though it omits permissions/auth and reversibility details.

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?

Three tight sentences, front-loaded with the core action, followed by requirements and the failure/recovery note. No filler, though the parenthetical naming of 'proposal Territory Solution' is slightly dense.

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?

An output schema exists so return values needn't be described, and the key error is covered. But for a destructive 8-param mutation with nested objects and 0% schema coverage, the description leaves most parameters and any permission/precondition context undocumented, so it is only adequately complete.

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 0% across 8 parameters, so the description must compensate, yet it names only branch_metadata and expected_master_revision. The six remaining params (master_ts, proposal_ts, map_session_id, master_ts_handle, proposal_ts_handle, expected_master_content_hash) are left entirely unexplained, including when the handle variants are used.

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 gives a specific verb+resource: 'Merges an edited branch... back into the master', and explicitly identifies the branch as the proposal from extract_tal_branch, which separates it from its counterpart sibling. It stops short of distinguishing itself from other mutation siblings like territory_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?

It embeds the tool in a workflow by naming extract_tal_branch as the source of the branch and states the recovery path when STALE_TS_REVISION is returned (a fresh extract is needed). It gives clear context but no explicit when-not-to-use or alternative-selection rule.

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