Zoom Active View To All Layers

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

Annotations already declare destructiveHint=false, idempotentHint=true, openWorldHint=false, so the safety profile is covered structurally. The description adds that the operation is 'real-time' against the live view, which is modest extra context, but it never explains what selection_only or symbolized_extent actually change in behavior.

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 compact sentence that is front-loaded, but the brevity comes at the cost of under-specification rather than being information-dense.

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 no output-schema explanation needed (one exists) the remaining gaps are large: 0% parameter coverage, no usage routing among numerous zoom siblings, and no note that an active view must exist for a 'real-time' operation. The definition is too thin for a 3-parameter tool in this crowded namespace.

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 all three parameters (aprx_path, selection_only, symbolized_extent), so the burden falls on the description. It only gestures at the selection case via '已有选择集' and says nothing about symbolized_extent or the required aprx_path, leaving two of three parameters unexplained.

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 (zoom) and resource (active map view to all layers/selection), which lets an agent distinguish this scope-based zoom from the singular arcgis_pro_zoom_active_view_to_layer or arcgis_pro_zoom_to_selection. It stops short of explicitly naming those siblings, so sibling differentiation is only implied by the word 'all'.

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 statement of when to use this tool versus arcgis_pro_zoom_to_layer, arcgis_pro_zoom_to_selection, or arcgis_pro_set_active_view_extent. The '或已有选择集' clause hints at the selection_only behavior but gives no conditional guidance or exclusions.

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