Raster Euclidean Distance

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

Annotations cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=true), signaling this writes output but is non-destructive and idempotent. The description adds only that outputs are verified item by item; it says nothing about overwriting existing rasters, required environments, or that direction rasters are only produced when the corresponding arg is supplied.

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 single front-loaded sentence is efficient with no wasted words, and the main purpose is stated first. It is arguably too terse for a 9-parameter geoprocessing tool, but as a conciseness measure there is little fat to trim.

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 9-parameter raster geoprocessing tool that produces output datasets, the description omits parameter semantics, environment handling, and when-to-use context. The output schema covers return values, but the invocation-relevant information is essentially absent.

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% across 9 parameters, and the description mentions no parameter at all — not cell_size, distance_method (PLANAR default), barriers, maximum_distance, or the three output paths. Compared to a 0-parameter baseline of 4, this leaves every parameter undocumented in prose.

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 specific verb+resource combination ('计算欧氏距离' = calculate Euclidean distance) and notes the optional direction/back-direction rasters, so the core operation is clear. However, it does not differentiate itself from close siblings like arcgis_pro_raster_distance_accumulation or arcgis_pro_calculate_distance_band, which an agent could easily confuse it with.

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 alternatives, no mention of prerequisites (e.g., source raster must be valid), and no exclusions. The '逐项核验全部输出' clause hints at an output-checking step but does not express a usage condition.

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