hotspot_analysis

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

No annotations provided, so the description carries the full burden. It discloses that the tool creates a feature class (write operation) and lists output fields, but does not mention prerequisites like ArcGIS license, performance implications, or error handling.

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?

Two concise sentences: the first states the core action and output, the second provides usage guidance and parameter summary. No wasted words.

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 (spatial statistics) and the presence of parameter descriptions in the schema, the description covers the algorithm, output fields, use case, and supported parameters. It is mostly complete, though it could mention that the input field must be numeric.

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?

The context indicates 0% schema description coverage, so the description must compensate. It adds context about the algorithm (ArcPy HotSpots) and result fields, and summarizes the key parameters (spatial conceptualization, distance method, optional distance band). However, it does not detail parameter constraints beyond what the schema already provides.

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 runs Getis-Ord Gi* hot and cold spot analysis using ArcPy HotSpots and writes a feature class with specific result fields (GiZScore, GiPValue, Gi_Bin). The purpose is specific and distinct from sibling tools like 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?

The description states when to use the tool ('identify statistically significant clusters') and mentions supported parameters, but does not explicitly say when not to use it or identify alternatives among sibling tools.

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