Map Pan To Extent

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=false, so the mutation/idempotency profile is covered structurally. The description's only additions are generic boilerplate ('返回可验证的结构化结果；写入和路径限制以服务能力为准') that does not say what state is modified, what permissions are needed, or what happens on a locked project. It adds essentially no behavioral context beyond the annotations.

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?

The text is short and front-loads the verb, 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 the specification an 8-parameter tool needs.

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 not be explained, and annotations cover the safety profile. What is missing is the information the agent actually needs: which parameter selects the target and what the extent coordinates mean. For an 8-parameter mutation with 0% schema coverage, this is significantly under-specified.

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?

The schema has 8 parameters with 0% description coverage, so the description carries the full documentation burden – and it delivers nothing. It never explains aprx_path, layout_name, mapframe_name, the xmin/ymin/xmax/ymax extent semantics, or the optional spatial_reference_wkid default of null. An agent cannot infer coordinate units or the meaning of the extent from the bare 'Xmin' titles.

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 ('平移地图' / pan the map), which is a valid minimal statement of purpose. However it omits the essential scope of the tool – panning a specific map frame (layout_name, mapframe_name) to a specific extent – and gives no way to distinguish it from close siblings like arcgis_pro_set_mapframe_extent, arcgis_pro_mapframe_extent, arcgis_pro_set_active_view_extent, or arcgis_pro_map_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 guidance, no prerequisites, and no mention of the near-duplicate sibling arcgis_pro_set_mapframe_extent that the agent must choose between. Only implicit usage is conveyed by the tool name itself.

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