Gp Spatial Join

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. The description's only behavioral claim — "returns verifiable structured results; write and path restrictions depend on service capability" — is generic filler that neither states that a new out_feature_class is created nor explains workspace/path requirements. No contradiction with annotations.

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?

Very short and front-loaded, but it is short in the wrong way: the second clause is generic boilerplate that would apply to nearly any geoprocessing tool and does not earn its place, while the one sentence that could carry information just repeats the tool name.

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?

An output schema exists, so return values need not be described. However, this is a write tool that creates a feature class, has three entirely undocumented required parameters at 0% schema coverage, and the description supplies no environment, path, or usage context — far short of what an agent needs to call it correctly.

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% for all three required parameters, so the description must compensate — and it does not. The parameter names (target_features, join_features, out_feature_class) are loosely self-describing, but nothing is said about join type/match option, field mapping, or output workspace, which are essential to invoking a spatial join correctly.

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?

"spatialgp spatial join" essentially restates the tool name/title rather than describing what a spatial join does (transferring attributes from join_features to target_features based on a spatial relationship). The prefix "ArcGIS Pro:" and the trailing boilerplate add no distinguishing content, and nothing separates it from siblings like arcgis_pro_gp_intersect or arcgis_pro_add_join.

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 guidance at all. It does not state when spatial join is preferable to attribute joins (add_join) or overlapping-geometry tools (gp_intersect, gp_union), nor does it mention prerequisites, spatial relationship options, or field mapping considerations.

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