zonal_statistics_as_table

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

No annotations are provided, so the description must carry the behavioral burden. It mentions the Spatial Analyst license requirement but does not disclose side effects like creating a new table, error if table exists without overwrite=true, or any modifications to input data. The 'overwrite' parameter in schema hints at destructiveness but is not explained.

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 long and front-loaded with the core functionality. It avoids fluff, but could be more efficient by integrating parameter hints or usage scenarios. Still, it is appropriately sized for a moderately complex tool.

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 rich input schema (with individual parameter descriptions), the description provides the essential purpose and license requirement but omits usage guidance relative to siblings and behavioral details like overwrite handling. The presence of an output schema (not shown) relieves the need to explain return values, but the description still lacks completeness in guiding the agent's decision.

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%, meaning the description adds no value beyond the schema's parameter descriptions. The description does not explain any of the six nested parameters (e.g., zone_field, in_value_raster), forcing the agent to rely solely on the schema. Although the schema provides good descriptions, the tool description fails to compensate for the low coverage.

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 calculates zonal statistics and writes results to a table using ArcPy Spatial Analyst ZonalStatisticsAsTable. It provides specific examples of zone datasets (districts, parcels, watersheds) and distinguishes from sibling 'zonal_statistics' by emphasizing output to a standalone table.

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 says 'Use this to summarize raster values by districts, parcels, watersheds, grid cells, or other zone datasets' but does not explicitly compare with similar sibling tools like 'zonal_statistics' or 'summarize_within'. It only notes the license requirement, leaving ambiguity about when to choose this tool over alternatives.

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