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

Beyond the annotations, the description discloses that the tool produces an extract in its own Territory Solution, returns branch_metadata needed by reintegrate_branch, and excludes locked territories by default when exclude_locked is true. It does not describe permission requirements or whether the source alignment is modified, but it adds useful behavioral context and does not contradict the annotations.

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 front-loaded with the core operation and is only three sentences long. Each sentence adds a distinct piece of value: purpose and selection, return metadata and reintegration dependency, and exclude_locked behavior.

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 tool has 10 parameters with no schema descriptions, and the description leaves most of them undocumented, including the sole required parameter tal_id. Output-schema existence covers return-value explanation, but for a mutation-like extraction tool the input-side gaps are too large for complete invocation guidance.

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 10 parameters, so the description must compensate. It explains only the branch-selection identifiers and exclude_locked, while required tal_id and most optional parameters such as delegate_ref, ts_handle, expected_revision, and expected_content_hash remain unexplained.

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 uses a specific verb and resource: extracting one regional branch of a hierarchical alignment into its own Territory Solution. It names the two branch-selection identifiers and distinguishes the operation from the related reintegrate_branch sibling, so an agent can identify the tool without opening the 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?

The description gives a clear use case: extract a region so a delegate can edit just that area, with branch_metadata retained for later reintegration. It implies the extract-then-reintegrate workflow, but it does not explicitly compare this tool to alternatives such as territory_split or realign or state when not to use it.

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