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

Annotations declare readOnlyHint=false, i.e. this is a mutating operation, yet the description's verb is 'Preview', which implies a read-only dry run. This directly contradicts the annotation, and the description says nothing about permissions, reversibility, or the effect of activation.

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?

A single front-loaded sentence with no filler, so it is structurally clean. However, it is under-specified rather than concise for an operation that requires four coordinated parameters.

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?

A mutating tool with four required parameters, no output schema, and no parameter descriptions needs the description to carry concurrency, idempotency, and safety context. The one sentence supplies none of it and additionally mislabels the 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?

Schema description coverage is 0% across four required parameters, and the description never mentions them. In particular, expectedCurrentPublicationId is clearly an optimistic-concurrency guard and idempotencyKey an operation-dedupe token, but neither concept is explained anywhere, leaving the agent to guess at invocation semantics.

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 states a specific action ('rolling a map forward or back to an immutable publication revision'), which is more than a tautology, but it labels the operation 'Preview' while the tool name and title say 'Activate'. An agent cannot reconcile whether this commits a change or merely shows one, so the purpose is misleading rather than clear.

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 when-to-use guidance, no mention of prerequisites, and no reference to alternatives such as map_publish or geobble_map_publication_list. The agent must infer the trigger condition entirely.

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