Zoom To Layer

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

Annotations already declare idempotentHint=true, destructiveHint=false, and readOnlyHint=false, so the safety profile is mostly covered. The description's second clause ('写入和路径限制以服务能力为准') adds a little context about service-dependent constraints, but it is generic boilerplate that does not explain zoom's effect on view state, the mapframe/layout coupling, or any auth requirement.

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?

It is short and front-loads the operation name, so it is not bloated. But the second sentence is generic filler that does not earn its place, and the brevity comes at the cost of under-specification.

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?

An output schema exists, so return values need no explanation. Still, for a 5-required-parameter view-mutation tool with 0% parameter coverage and no usage routing, the description is too thin to let an agent invoke it correctly.

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?

Five required parameters with 0% schema description coverage, and the description names none of them. The agent gets no explanation of aprx_path, map_name, layer_name, layout_name, or mapframe_name, nor how they relate to each other, so the description fails to compensate for the schema gap.

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 verb+resource ('缩放图层' / zoom to layer), so the basic operation is identifiable. However, it offers no differentiation from close siblings such as arcgis_pro_zoom_active_view_to_layer, arcgis_pro_sdk_zoom_layer, or arcgis_pro_zoom_to_selection, leaving the agent unable to tell them apart from the text alone.

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 explicit when-to-use, when-not-to-use, or alternative-routing guidance. Given several near-identical zoom siblings, this absence is a real gap rather than an implied convention.

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