Gp Clip Raster Checked

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

Annotations already declare idempotentHint=true, destructiveHint=false, and write-capable (readOnlyHint=false). The description adds real context beyond that: it discloses the output format (single-band north-up GeoTIFF, file-mode), the immutable run ID concept, and that full-domain quality checks are performed. It does not say what the checks enforce, what failures look like, or where output is written.

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 dense sentence with no filler, and the key constraints (file output, geographic assumptions, validation) are front-loaded. It is information-packed but readable, though the stacked noun phrases make it slightly hard to parse.

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 an 11-parameter mutation tool with nested asset objects and 0% schema documentation, the description omits critical calling details such as how the AOI is specified, what minimum_coverage does, and how run_id drives idempotency. An output schema exists, so return values need not be explained, but the input contract remains largely undocumented.

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 11 parameters, so the description carries the full burden, but it only gestures at them: 'explicit AOI' (clip_mode/rectangle/boundary_asset), 'reference grid' (grid_asset), 'immutable run ID' (run_id), and 'quality checks' (validity/minimum_coverage/maximum_output_cells). It gives no meaning for clip_mode values, rectangle_crs, or minimum_coverage thresholds, leaving most parameters opaque.

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+resource ('clip raster') and adds meaningful qualifiers (file-mode, single-band, north-up GeoTIFF, quality checks) that distinguish it from a plain clip. However, it never explicitly names or contrasts with the sibling arcgis_pro_gp_clip_raster, so the 'checked' variant's role is left to inference.

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 prerequisites, and no mention of the obvious alternative arcgis_pro_gp_clip_raster. The reader must guess why they would pick the 'checked' tool over the plain clip tool.

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