Set Active View Extent

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

Annotations already declare not-readOnly, non-destructive, idempotent, and closed-world, so the safety profile is covered. The description adds that the change hits the live/active view in real time, which is beyond the annotations, but it omits side effects like whether the change persists to the project or how the extent is projected.

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 clause that states the action immediately, with the preserve_scale condition appended. No filler, though it is arguably too terse for a 7-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?

For a 7-parameter mutation tool in a dense sibling set, the description leaves usage routing and most parameter meaning unexplained. An output schema exists so return values needn't be described, but the gaps in routing and parameters make it under-specified overall.

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 7 parameters. The description only restates preserve_scale semantics (already implied by its name/default) and says nothing about spatial_reference_wkid, units, or the role of aprx_path, leaving the two non-obvious optional parameters undocumented.

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 names a specific verb pair (set/pan) and the precise resource (ArcGIS Pro's current map view extent), plus a conditional behavior for preserve_scale. It clearly conveys what the tool does, but never differentiates it from similar siblings such as arcgis_pro_set_mapframe_extent, arcgis_pro_map_pan_to_extent, or arcgis_pro_set_active_view_camera.

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 vs. when-not-to-use guidance. With several extent/camera siblings in the catalog, an agent gets no signal on why it should pick 'set active view extent' over 'map pan to extent' or 'set active view camera'.

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