Raster Stream To Feature

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, so the agent knows this writes a dataset non-destructively and is repeatable. The description adds only that the output is a *new* polyline feature class and that a verification step occurs, which is consistent with the annotations but adds little beyond them. Nothing is said about overwrite behavior, required extensions, or whether existing outputs are replaced.

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, front-loaded with the core transformation and free of padding, which is good. But for a five-parameter raster hydrology tool with a required companion raster, one sentence is under-specified rather than concisely complete.

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 the definition still leaves an agent unable to call the tool correctly: the required flow-direction raster and its provenance are never mentioned, and no sibling routing is given. For a write-producing raster analysis tool the description is materially incomplete.

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 5 parameters, so the description carries the full explanatory burden. It gestures at the stream raster and the output polyline feature class but says nothing about the required in_flow_direction_raster (the most consequential parameter), the simplify flag, or the environment object. Two of five parameters are weakly implied at best.

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 concrete verb and a concrete input/output pair: convert a stream (river-network) raster into a new polyline feature class, plus a verification step. That is clearly more specific than a tautology. It does not, however, distinguish this tool from the several other raster-to-vector conversion siblings such as arcgis_pro_gp_raster_to_polygon or arcgis_pro_gp_feature_to_line, so it lands at 4 rather than 5.

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 statement of when to use this tool versus alternatives (raster_to_polygon, stream_order, basin) and no mention of the essential prerequisite that a flow-direction raster must already exist (typically produced by arcgis_pro_raster_flow_direction). The only implied guidance is the input type. That is below the minimum-viable bar.

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