Raster Distance Accumulation

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered. The description adds only that optional derived direction/location rasters may be produced and that results are 'verified', but discloses nothing about cost surfaces, barriers, environment handling, or whether existing outputs are overwritten.

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?

A single short sentence with no padding and the core operation front-loaded. But it is under-specified rather than genuinely concise: the brevity comes at the cost of the parameter and usage information the agent 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, but a 16-parameter geoprocessing tool with 0% schema coverage and no usage guidance is left materially under-described; an agent cannot tell how to configure cost/barrier/surface inputs or which optional outputs to request.

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?

16 parameters with 0% schema description coverage, so the description carries the full burden. It alludes to only three of them (back direction, source direction, source location outputs) and says nothing about in_cost_raster, in_barrier_data, in_surface_raster, in_vertical/horizontal_raster, distance_method, or the accumulation multipliers, leaving most parameters undocumented anywhere.

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?

It gives a specific verb+resource (计算距离累积 / calculate distance accumulation) and names the optional derived outputs (back/source direction/location rasters). However it does not distinguish this from siblings like arcgis_pro_raster_euclidean_distance, arcgis_pro_raster_optimal_path_as_line or arcgis_pro_calculate_distance_band, which all concern distance surfaces, so an agent cannot confidently route between them from this text alone.

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?

The description states what is computed but never says when to choose this tool over alternatives or what inputs/prerequisites are needed. '并核验' (and verify) hints at a validation step but no condition or alternative is named.

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