Set Map Reference Scale

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, covering the safety profile. The description adds that results are structured/verifiable and that write and path restrictions depend on service capabilities, but these remarks are generic rather than specific to setting a map reference scale. No annotation contradiction is present.

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: it front-loads a vague 'set map' statement and then adds generic boilerplate about structured results and service restrictions. The sentences do not earn their place because they fail to convey the actual operation.

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?

This is a mutation tool with three required parameters, no schema descriptions, and no operation-specific explanation in the description. Although an output schema exists and annotations cover the safety profile, the description still omits what the tool changes, what reference_scale means, and how the map and project path parameters relate, leaving the definition incomplete for correct invocation.

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?

There are three required parameters (aprx_path, map_name, reference_scale) with 0% schema description coverage. The description provides no meaning, format, or expected value for any of them, so it does not compensate for the schema's lack of parameter documentation.

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 says only 'ArcGIS Pro：设置地图' (ArcGIS Pro: set map), which states a generic platform and verb but omits the distinguishing operation 'reference scale' that appears in the tool name and title. An agent cannot tell from this description what specific map property is being set or how it differs from many sibling map-setting tools.

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 guidance, no alternatives, and no exclusions are provided. The only contextual phrase, '写入和路径限制以服务能力为准' (write and path restrictions depend on service capabilities), is not usage guidance and does not help an agent choose this tool over siblings.

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