flow_direction

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

Without annotations, the description carries the full burden of behavioral disclosure. It mentions that it writes an output raster, requires a license, and can optionally force edge cells to flow outward. However, it does not address whether the input is modified, error handling, performance implications, or the format of the output raster.

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 two sentences long, front-loaded with the main action and purpose. Every sentence provides essential information without redundancy or unnecessary detail.

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 tool that writes a file, the description covers the primary output and behavior. However, given the complexity of hydrologic modeling and the presence of many sibling tools, the description could benefit from mentioning the output raster's cell values or format. Additionally, it does not explain how the tool handles edge cells or the interaction with other hydrologic tools.

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?

The schema descriptions are minimal (e.g., 'Absolute path to the existing input raster dataset'), and the tool description only elaborates on two parameters (out_raster and force_flow) indirectly. With a schema description coverage of 0%, the description fails to compensate adequately for the four parameters, leaving in_raster and overwrite without additional context.

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 clearly states the tool derives a hydrologic flow-direction raster from an elevation raster using a specific ArcPy function. It lists typical use cases like flow accumulation and watershed delineation, which helps distinguish from sibling tools that perform other hydrologic analyses. However, it does not explicitly contrast with tools like fill_sinks or slope_analysis.

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 specifies when to use the tool (prior to flow accumulation, watershed delineation, etc.) and notes the prerequisite of a Spatial Analyst license. It does not mention when not to use it or provide alternatives, which limits its guidance for selection.

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