activate_map

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that this changes UI state and must precede camera/export commands, but says nothing about failure modes, whether an already-active map errors, or what state changes persist — meaningful gaps for a state-changing tool with zero annotation coverage.

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?

Two compact sentences with zero filler, and the effect (activate view) is front-loaded ahead of the prerequisite note. Every clause earns its place.

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?

With one parameter, an output schema present, and the sequencing constraint stated, the definition covers what an agent needs to invoke it correctly. Only the error/edge-case behavior is absent, which is a minor gap given the output schema carries return information.

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?

Only one parameter and schema description coverage is 100%, so the schema already fully documents map_name as 'Map to activate.' The description adds no syntax, naming, or matching semantics beyond that, making baseline 3 appropriate.

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: 'Open/activate a map's view in the ArcGIS Pro UI'. This is clearly distinct from adjacent siblings like list_maps, get_map_view and set_map_view, though the description never explicitly contrasts itself with them.

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?

Gives explicit prerequisite ordering: 'Needed before camera commands and export_map_view'. That tells the agent when this call is required rather than optional. It stops short of naming exclusion cases (e.g. what happens if the map is already active), so it is clear context without full when/when-not guidance.

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