Raster Stream Order

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

Annotations already declare the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=false), so the bar is lowered. The description adds nothing behavioral beyond the method names: it does not say whether an existing out_raster is overwritten, whether the stream and flow-direction rasters must share a grid/extent, or what environment settings affect execution.

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, so nothing is wasted. However, at this length the sentence is under-specified rather than genuinely concise, leaving no room for the required workflow or parameter context.

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?

The presence of an output schema means return values need not be described, and annotations cover safety. But for a multi-input raster geoprocessing tool with 5 parameters and zero schema documentation, the description omits input requirements, algorithm choice implications, and output behavior, leaving significant gaps.

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 burden. It only gestures at order_method by naming STRAHLER/SHREVE; in_stream_raster, in_flow_direction_raster, out_raster, and environment are entirely unexplained in both schema and description.

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 gives a specific verb+resource ('计算河网等级栅格' = compute a stream-network order raster) and names the two supported algorithms (STRAHLER/SHREVE), so an agent knows exactly what is produced. It does not, however, differentiate itself from adjacent hydrology siblings such as flow_direction, flow_accumulation, or stream_to_feature.

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 when-to-use guidance, no mention of prerequisites (a flow-direction raster and a stream raster are required inputs), and no pointer to which sibling to run before or after this step. The agent must infer the whole hydrology workflow on its own.

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