raster_to_polygon

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

With no annotations, the description carries full burden. It discloses the high-level operation (reads in_raster, writes out_features) and references the ArcPy function, but does not detail side effects (creation of a new feature class, overwrite behavior, permissions, or impact on existing data). The overwrite parameter is documented in the schema, but the description misses emphasizing the destructive potential.

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 extremely concise: two sentences that efficiently state the action, the underlying tool, specific use cases, and input/output. No superfluous words; every sentence adds value.

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 that the input schema is detailed and an output schema exists (though not shown), the description provides a sufficient high-level overview. It covers the core functionality and typical applications. Minor omissions include handling of NoData, attribute preservation, and coordinate system behavior, but these are not critical for basic understanding.

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 thorough descriptions for all parameters (e.g., simplify, in_raster, out_features). The tool description adds only a summary ('Reads in_raster and writes out_features'), which does not significantly enhance understanding beyond the schema. Since schema description coverage is high (all parameters have descriptions), 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 action ('Convert raster zones or classes to polygon features') and the specific resource ('using ArcPy RasterToPolygon'). It distinguishes from siblings by providing examples ('classified rasters, suitability classes, land-cover codes, or cell regions') and contrasts with the inverse tool polygon_to_raster, which is in the sibling list.

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 clear use cases ('Use this to vectorize classified rasters, suitability classes, land-cover codes, or cell regions') and suggests appropriate contexts ('GIS editing, overlay, and cartographic workflows'). However, it does not explicitly state when not to use this tool or mention alternatives like polygon_to_raster for reverse conversion.

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