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

Annotations declare readOnlyHint=false and the name says 'activate', but the description describes a 'Preview' — implying a no-side-effect read. With no mention of permission requirements, reversibility, or what happens to the current live publication when rolling back, the description actively misleads rather than informs.

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 short, front-loaded sentence with no padding. Its problem is under-specification, not verbosity, so structure itself is fine.

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 four-required-parameter mutation with no output schema and no parameter documentation, the description supplies no information an agent needs: no concurrency contract, no idempotency behavior, no indication of what the 'preview' returns or whether a second call commits the change.

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 explains none of them. In particular, 'expectedCurrentPublicationId' (an optimistic-concurrency guard) and 'idempotencyKey' are critical to calling the tool correctly, and neither is mentioned.

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 sentence names a resource ('map publication revision') and a directionality ('forward or back'), but the verb is 'Preview', which contradicts the tool name and title ('Activate'). An agent reading the description would reasonably conclude it is a dry-run, which is not what the name promises. The action it actually performs is never stated unambiguously.

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 guidance on when to call this versus its obvious siblings (map_publish, map_publication_list, confirm_action, cancel_action). The word 'Preview' even implies a two-phase confirm flow that is never explained, leaving the agent unable to tell whether a follow-up activation call is needed.

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