Raster Optimal Path As Line

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

Annotations declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, so the safety profile is partly covered. The description adds only a vague 'verify output' note and says nothing about creating a new output dataset, overwrite behavior, or required inputs being schema-consistent with each other.

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 front-loaded sentence with no filler, stating the inputs before the output. It is efficient, though the terseness is partly a symptom of under-specification rather than disciplined brevity.

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 for an 8-parameter, 0%-coverage tool with no usage or behavioral detail, the description is far too thin. An agent lacks the information needed to invoke it correctly beyond the four required argument names in the schema.

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 with 0% schema description coverage, so the description carries the full burden, yet it only implicitly references the two input rasters. It says nothing about path_type, destination_field, create_network_paths, environment, or which parameters are required, leaving most parameters undocumented.

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 names a specific verb (生成/generate) and a specific resource (最优路径线/optimal path line) and identifies the two source rasters (distance accumulation, back direction). It is clear what the tool produces, though it does not distinguish itself from sibling raster/GIS tools such as raster_distance_accumulation.

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 prerequisites (e.g. that distance accumulation and back direction rasters must be generated first), and no exclusions. The agent must infer usage entirely from the operation name.

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