Raster Flow Accumulation

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

Annotations (readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=false) already declare this is a non-destructive, idempotent write operation on a closed-world local resource. The description adds that output verification is performed, which is useful but minor. It doesn't elaborate on what verification entails, or how the environment parameter affects behavior. With annotations covering the safety profile, a 3 is appropriate.

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 efficiently states the main output, optional inputs, and verification step.

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 hydrology raster tool with 6 parameters, no schema descriptions, and no parameter documentation in the description, the definition is incomplete. While an output schema exists, the lack of guidance on flow_direction_type, data_type options, and environment configuration leaves the agent unable to correctly invoke the tool without external knowledge.

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%, with 6 parameters (input flow direction, output accumulation, weight raster, flow direction type, data type, environment). The description only alludes to a weight raster and environment, leaving the most critical parameter – flow_direction_type with default D8 – entirely unexplained in both schema and description. An agent cannot know the available flow direction algorithms or their impact.

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 (compute/calculate 计算) and resource (flow accumulation raster 流量累积栅格), which distinguishes it from sibling hydrology tools like flow_direction or watershed. It is clear what the tool produces, though it doesn't explicitly differentiate its position in the hydrology workflow relative to those siblings.

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 mentions optional weight raster and controlled analysis environment, and output verification, but provides no guidance on when to use this tool versus arcgis_pro_raster_flow_direction, arcgis_pro_raster_watershed, or arcgis_pro_gp_run_tool. An agent must infer usage context.

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