Find Point Clusters

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true. The description adds the Advanced license requirement and the need to verify distance/time parameters, which is useful context, but does not describe output creation, failure modes, or other side effects.

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?

One short sentence, front-loads purpose and then prerequisites, with no filler. It may be too terse for an 8-parameter tool, but that is more a completeness issue than conciseness.

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 an 8-parameter geoprocessing tool with 5 required parameters and 0% schema description coverage, the description leaves most parameter meanings and invocation context unexplained. Output schema covers return values, but the definition is not complete enough for reliable invocation.

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?

With 0% schema description coverage across 8 parameters, the description must carry parameter semantics. It only references distance/time parameters and implicitly clustering method, without explaining input_points, output_features, minimum_points, search_distance format, search_duration, environment, or use_time semantics.

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?

States a specific verb and resource: clustering points with DBSCAN/HDBSCAN. Naming the algorithms helps distinguish it from other clustering siblings like multi-distance spatial clustering, but it does not explicitly contrast alternatives.

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?

Provides a prerequisite (verify Advanced license) and highlights distance/time parameters, implying usage conditions. However, it does not state when to choose this tool over sibling clustering tools or when not to use it.

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