Set Mapframe Extent

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description adds only generic boilerplate ("returns verifiable structured results; write and path restrictions depend on service capabilities") that discloses nothing concrete about what is mutated, required permissions, or failure modes.

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 action, but the second clause is generic filler rather than useful detail. Brevity here reflects under-specification rather than efficient, information-dense wording.

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 an 8-parameter write operation touching an .aprx file on disk, the description omits the coordinate semantics, the identity of the target (path/layout/mapframe), and any prerequisites. The existence of an output schema covers return values, but everything an agent needs to invoke this correctly is missing.

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?

Eight parameters (7 required) with 0% schema description coverage — the schema provides only titles like "Xmin"/"Aprx Path" and no semantics. The description contributes nothing about coordinate units, spatial reference handling for spatial_reference_wkid, or path/layout/mapframe naming, so it fails to compensate for the coverage 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?

"设置地图框" (set the mapframe) merely restates the tool name/title and never mentions that it sets the mapframe's extent to specific xmin/ymin/xmax/ymax coordinates. The agent cannot distinguish this from arcgis_pro_mapframe_extent (read) or arcgis_pro_mapframe_zoom_to_bookmark based on the text.

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 guidance on when to use this tool versus siblings such as arcgis_pro_mapframe_extent (get the current extent), arcgis_pro_mapframe_zoom_to_bookmark, or arcgis_pro_set_map_reference_scale. No preconditions (project open, layout/mapframe must exist) are stated.

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