Spatially Constrained Multivariate Clustering

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

Annotations declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=false, indicating a non-destructive, idempotent analysis operation. The description adds little beyond reiterating the operation name and noting that outputs (features and evaluation table) should be verified. It does not disclose execution time, resource requirements, or side effects, but it does not contradict annotations either.

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 a single short sentence, but it is under-specified rather than concise. It lacks front-loaded, actionable information and wastes no words only because it provides almost no content. It does not follow a useful structure (e.g., purpose, key inputs, outputs).

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 (13 parameters, spatial/scale constraints, output features and table, permutation testing), the description is completely inadequate. It fails to explain what the tool does, how to configure constraints, what the outputs represent, or any prerequisites. Although an output schema exists, the description still must convey the tool's purpose and parameter semantics, which it does not.

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%, with 13 parameters and 4 required. The description provides no parameter information whatsoever—no mention of input features, analysis fields, constraint fields, spatial constraints, size constraints, number of clusters, or any other parameter. For a tool with such a rich parameter set, this is a severe gap; the description does nothing to clarify or supplement the parameter meanings.

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 is essentially a restatement of the tool name/title ('spatially constrained multivariate clustering') plus a vague mention of validating outputs. It does not state what the tool actually produces (e.g., a feature class with cluster assignments) or how it differs from siblings like arcgis_pro_multivariate_clustering or arcgis_pro_find_point_clusters. An agent cannot reliably distinguish this from other clustering tools based on the 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?

No explicit when-to-use or when-not-to-use guidance is provided. It does not mention alternatives such as arcgis_pro_multivariate_clustering (unconstrained clustering) or arcgis_pro_generate_spatial_weights_matrix, leaving the agent to infer the appropriate context. The brief mention of '核验要素和评估表输出' is more about output behavior than usage context.

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