slope_analysis

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

With no annotations provided, the description carries the full burden. It discloses the license requirement (Spatial Analyst), output type (slope raster), and output measurement options (degrees, percent rise) with z_factor usage. It does not explicitly state that the input raster is unchanged, but the word 'derive' implies a read-only operation. The description could mention idempotency or side effects, but the behavioral disclosure is mostly adequate.

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 very concise, consisting of three short sentences. It front-loads the core function ('derive slope') and efficiently adds usage context and behavioral notes. Every sentence adds value without redundancy or unnecessary detail.

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 (a GIS spatial analysis tool with five parameters) and the presence of an output schema, the description provides necessary context: the core functionality, typical use cases, and license requirement. It does not explain return values (the output schema likely handles that) or all prerequisites (e.g., that in_raster must be a single-band elevation). However, the description is largely complete for an agent to select and invoke the tool correctly.

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 provides detailed descriptions for all parameters (in_raster, out_raster, z_factor, overwrite, output_measurement) including defaults and constraints. The description repeats some schema information (e.g., degrees/percent rise, z_factor) but adds the context of using ArcPy Spatial Analyst. Since schema coverage is effectively 100%, the description adds minimal extra meaning, resulting in a baseline score of 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?

Description clearly states the tool derives slope from an elevation raster using ArcPy Spatial Analyst, specifying the resource (elevation raster), action (derive slope), and output format (slope raster in degrees or percent rise). It provides context for use in terrain, hydrology, etc., which helps the agent understand its domain. However, it does not explicitly distinguish this tool from siblings like aspect_analysis or hillshade, which limits precision.

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 lists application areas (terrain, hydrology, accessibility, hazard, site suitability) implying when to use. It also mentions the requirement for a Spatial Analyst license. However, it provides no guidance on when not to use this tool or alternatives (e.g., for non-raster slope calculations). This lack of exclusions and alternative references reduces the score.

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