Gp Spatial Autocorrelation

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only a generic note about 'verifiable structured results' and write/path restrictions, without describing output structure, permissions, or operational constraints. It does not contradict the annotations, but it adds negligible behavioral detail.

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 (two sentences), but neither sentence earns its place: the first is a tautological restatement of the tool name, and the second is generic boilerplate about service capabilities. Useful information is not front-loaded because there is no useful information at all.

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 7-parameter geoprocessing tool with mandatory inputs and an output schema, the description provides no information about inputs, outputs, or execution context. It is completely inadequate for an agent to select or invoke the tool correctly without external documentation.

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 7 parameters, and the description mentions none of them. Required inputs (in_features, input_field) and optional concepts (distance_band, standardization, conceptualization, etc.) are completely undocumented, so the description fails to compensate for the schema gap.

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 restates the tool name ('spatial autocorrelation') without a clear verb or specific outcome. It does not explain that the tool computes a spatial autocorrelation statistic (e.g., Moran's I) or how it differs from sibling tools like hot spots or cluster outlier analysis. An agent cannot determine the tool's actual computational purpose from this text alone.

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 when-to-use guidance, no conditions for selecting this tool over alternatives such as arcgis_pro_gp_hot_spots or arcgis_pro_gp_cluster_outlier, and no prerequisites. The description only supplies generic boilerplate about service capabilities, leaving the agent to infer usage entirely from the tool name.

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