Set Map Spatial Reference

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds only a generic caveat that 'write and path restrictions depend on service capabilities' and that structured results are verifiable, without specifying permissions, path constraints, or mutation effects. This is weak added 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 description is short, but it is under-specified rather than concise. Both sentences are boilerplate that do not front-load the operation's essential meaning or the required inputs.

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 parameterized mutation tool with three required arguments and 0% schema description coverage, the description should explain what setting a spatial reference means and what inputs are needed. It fails to do so; only the existence of an output schema relieves the burden of describing return values.

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% for all three required parameters (aprx_path, map_name, wkid). The description mentions none of them and provides no format, meaning, or value guidance for wkid or the path/map-name arguments, leaving the agent with no semantic information beyond parameter names.

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 only says 'Set map' (设置地图), which is a vague restatement of the title's action but omits the key resource qualifier 'spatial reference'. It does not distinguish this tool from siblings like arcgis_pro_set_map_reference_scale or arcgis_pro_set_map_default_camera, so an agent must open the schema to learn what map property is being set.

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?

No when-to-use, when-not-to-use, or alternative guidance is given. The description provides no context for choosing this tool over the many other map-configuration siblings.

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