Raster Flow Direction

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

Annotations already declare the write-oriented profile (readOnlyHint=false), idempotency, and non-destructiveness. The description adds algorithm choices, an optional drop raster, and output verification, but does not disclose overwrite behavior, permissions, or input raster requirements beyond what annotations provide.

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; it states the core operation, the main algorithm options, and one optional output efficiently. It is appropriately concise, though compressed for a six-parameter tool.

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 complex raster geoprocessing tool with six parameters and no schema descriptions, the description omits required input semantics, environment handling, force_flow behavior, and output overwrite/verification details. An output schema exists, so return-value explanation is not required.

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 six parameters, so the description must carry the burden. It partially explains flow_direction_type values (D8/MFD/DINF) and out_drop_raster optionality, but leaves required in_surface_raster, out_flow_direction_raster, force_flow, and environment unexplained.

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?

States a specific verb (计算/calculate) and resource (流向/flow direction), and names the supported algorithms D8/MFD/DINF plus an optional drop raster. It is clear what the tool does, but it does not explicitly distinguish itself from adjacent raster hydrology siblings such as flow_accumulation or watershed.

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?

Provides no when-to-use, when-not-to-use, prerequisite, or alternative guidance. It only notes an optional output, which is a capability statement rather than usage context.

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