Gp Zonal Statistics As Table

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true and openWorldHint=false, so the safety profile is covered. The description's only addition is the generic clause that write and path restrictions follow service capabilities; it does not say what table is created, where out_table is written, or how failures are surfaced, so the added context is thin boilerplate.

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 short but under-specified rather than concise: two terse, partly boilerplate clauses that carry almost no actionable information. Brevity here reflects missing content, not efficient front-loading.

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?

For a geoprocessing tool with six parameters, four of them required, zero schema descriptions, and an output schema, the definition is grossly incomplete. An agent cannot reliably select or invoke it from this text; the output schema covers return values but nothing explains inputs or usage.

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% across six parameters, and the description supplies no meaning for in_zone_data, zone_field, in_value_raster, out_table, statistics_type, or ignore_nodata. The description does nothing to compensate for the undocumented schema, leaving the agent to guess parameter roles and accepted values.

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?

"ArcGIS Pro：zonal表" essentially restates the tool name/title ("Gp Zonal Statistics As Table") without naming a distinct verb and resource or the statistical output it produces. It gives no basis for distinguishing this from the many other raster/zonal/statistics siblings such as arcgis_pro_gp_statistics or arcgis_pro_raster_cell_statistics.

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?

There is no statement of when to use this tool versus alternatives, no prerequisites (e.g. that it needs a zone dataset plus a value raster), and no mention of when a plain statistics or cell-statistics tool would be preferable. Only the vaguest implicit usage context is conveyed by the word "zonal".

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