contour_lines

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

With no annotations, the description must disclose behavioral traits. It mentions the requirement for a Spatial Analyst license and that it writes a polyline feature class. However, it does not discuss performance, error conditions, or the effect of overwriting existing outputs, which limits its transparency.

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 concise at three sentences, each serving a distinct purpose: tool action, use cases, and requirements. It is well-structured and front-loaded with the primary function.

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 has an output schema (not shown) and the input schema is detailed, the description covers the core functionality and requirements. It could mention the output schema briefly, but the overall completeness is high for a tool with structured metadata.

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?

Although the input schema includes descriptions for each parameter, the context indicates 0% schema description coverage. The tool description does not elaborate on parameter meanings beyond mentioning 'DEM raster' and 'elevation isolines', but the schema itself is explicit. Thus, the description adds little beyond the schema.

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 creates vector elevation isolines from a DEM raster using ArcPy Spatial Analyst Contour. It provides specific use cases: cartographic contours, terrain analysis inputs, elevation reference lines. This distinguishes it well from sibling tools like raster_calculator or slope_analysis.

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 explicitly states when to use the tool ('Use this to generate...') and lists common applications. However, it does not mention when not to use it or provide alternatives, such as other raster-to-vector tools or methods for contour generation.

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