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

Annotations already declare destructiveHint=true and idempotentHint=false, and the description adds real behavioral context beyond them: the live map jumps to the new center/zoom, the server computes classification breaks and returns per-class counts, only one classification per channel per layer is allowed, clear:true removes one, and classification without point_layer is a project-level setting that does not color points. It does not explain the merge_strategy semantic or what the destructive refresh actually overwrites, which keeps it from a 5.

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 purpose is front-loaded, but the body is a single dense run-on with many parenthetical clauses and inline enumerations that make it hard to scan for a specific parameter. Every element is arguably informative, but the lack of any structuring (bullets, grouping of related settings) costs readability on a 15-parameter tool.

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 need not be spelled out, and the description does valuable work covering layer and symbology semantics. However, for a destructive, non-idempotent mutation it is silent on merge_strategy, expected_revision, and expected_content_hash, which look like concurrency/conflict-control parameters an agent must understand to call this safely.

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% with 15 parameters, so the description carries the full burden, and it defines most of them in prose: project_name, loaded_part_layers (including the [] special case), active_part_layer, active_tal_id, center, zoom, point_layer_classifications sub-fields (method enum values, class_count range, channel, colors/sizes/shapes), classification, and the map_session_id/ts_handle/ts inputs. It leaves presentation, merge_strategy, expected_revision, and expected_content_hash entirely unexplained, which is a notable gap for a destructive write.

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 and resource ("Updates map settings on the Territory Solution and refreshes the live map") and then enumerates exactly which settings are in scope, from heading and part layers to point symbology. It is clearly a map-configuration tool, though it never names the nearest sibling (set_map_state) to draw a boundary, so sibling differentiation relies on the reader knowing the other 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?

There is no explicit when-to-use or when-not-to-use guidance, and no alternative tool is named despite siblings like set_map_state, ensure_map_viewer, and get_map_visualization occupying similar space. The closing "Input: map_session_id (the live map), ts_handle, or ts" is input-selection help, not usage routing, so an agent gets no rule for choosing this tool over a neighbor.

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