extract_by_mask

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

No annotations are provided, so the description carries the full burden. It discloses license requirements and path constraints, but does not detail behaviors such as whether the input raster is modified, error handling, or performance implications of the extraction operation.

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?

The description is three sentences, front-loaded with the core action and use cases. Each sentence provides distinct value without redundancy. It could be slightly more concise but is well-structured.

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?

Given the tool's complexity and the presence of an output schema, the description adequately covers license, path constraints, and typical use. It does not address unsupported input types or coordinate system handling, but is sufficient for an experienced user.

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?

The input schema already has detailed descriptions for each parameter. The description adds no new parameter-level meaning beyond reiterating PathGuard constraints. With high schema coverage (100% of parameters have descriptions), the baseline is 3.

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 clearly states the tool extracts raster cells inside a mask using ArcPy Spatial Analyst ExtractByMask, with specific use cases like clipping elevation, imagery, and land-cover. However, it does not distinguish itself from the sibling tool clip_raster, which may perform a similar function.

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 provides when to use the tool (to clip raster data to a study area before analysis) and mentions prerequisites (Spatial Analyst license, PathGuard roots). It lacks explicit guidance on when not to use it or comparison to alternatives like clip_raster.

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