Raster Watershed

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, openWorldHint=false, so the safety profile is covered. The description adds only the mild detail that the output is verified; it says nothing about overwrite behavior for an existing out_raster, environment handling, or failure modes, which matters for a tool that writes a dataset.

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, and the core operation leads. It is efficient, but the brevity here reflects under-specification rather than tight writing.

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?

With five parameters, 0% schema description coverage, and no annotations on data handling, this terse sentence is not enough for an agent to call the tool correctly. The existence of an output schema excuses it from documenting return values, but it still omits prerequisites, parameter meaning, and output-location behavior.

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%, so the description must carry the burden, but it only references two of the five inputs (flow direction raster, pour points) in generic terms. The pour_point_field, out_raster, and environment parameters receive no explanation at all, leaving their expected values and interaction 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?

The description gives a specific verb+resource: generate a watershed raster from a flow-direction raster and pour points, plus verify the output. An agent can tell this apart from generic raster tools, though it never names the closely related siblings (raster_basin, raster_stream_order) that a user might confuse it with.

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, no prerequisites (it implicitly requires a flow-direction raster, typically from raster_flow_direction, and often a snapped pour point), and no guidance on when watershed differs from basin. Usage is only inferable from the tool name.

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