Gp Cluster Outlier

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=false, so the safety profile is covered elsewhere. The description adds only a vague 'writing and path limits follow service capabilities' line, with no specifics on output overwrite behavior, required permissions, or runtime cost of permutation tests.

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 text is short and not padded, which is fine, but the brevity is under-specification rather than disciplined concision. It is front-loaded with a redundant restatement of the tool name rather than useful content.

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 a 9-parameter mutation tool with 0% schema coverage and many competing spatial-analysis siblings, the description is far too thin to call this correctly. An output schema exists so return values need not be explained, but input semantics and usage context remain unaddressed.

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 9 parameters, so the description must compensate and it does not. Critical parameters such as conceptualization, distance_band, distance_method, standardization, apply_fdr, and number_of_permutations are entirely undocumented in both schema and description, leaving an agent unable to configure the tool.

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 largely restates the tool name ('ArcGIS Pro: clustergp cluster outlier') without stating what the analysis produces. It never says this performs a Cluster and Outlier Analysis (Anselin Local Moran's I), so an agent cannot distinguish the output semantics from siblings like arcgis_pro_gp_hot_spots or arcgis_pro_gp_spatial_autocorrelation.

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 when-to-use, when-not-to-use, or alternative-tool guidance is given. With numerous nearby spatial-statistics siblings (hot_spots, optimized_hot_spots, spatial_autocorrelation), the absence of routing guidance is a real gap.

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