spatial_join

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

No annotations are provided, so the description carries full burden. It discloses the operation (reads target/join features, writes out_features) and mentions PathGuard root constraints. However, it does not describe side effects (e.g., no modification of inputs), permission requirements, behavior on empty features, or details about overwrite and match_option behavior beyond the schema.

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 concise with two sentences: the first states the core action and technology, the second provides usage context. It is front-loaded, contains no redundant information, and every sentence adds value.

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?

While the description covers the basic operation and PathGuard roots, it omits important details for a spatial join tool: explanation of different match options (e.g., INTERSECT vs WITHIN), join operations (one-to-one vs many), overwrite behavior, and output schema characteristics. With no annotations and no output schema visible, the description should provide more context to ensure correct 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?

The schema descriptions (e.g., for target_features, join_features, out_features) already provide clear parameter meanings. The description adds some context ('reads target_features and join_features and writes out_features inside PathGuard roots') but does not significantly enhance understanding beyond the schema, which has high coverage.

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 purpose: joining attributes from one feature layer to another based on spatial relationships using ArcPy SpatialJoin. It specifies the action (join), resources (feature layers), and distinguishes from other spatial tools like intersect_features or spatial_autocorrelation by explicitly mentioning counting, summarizing, or transferring attributes.

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 provides clear usage context: 'Use this to count, summarize, or transfer nearby, contained, intersecting, or matching feature attributes into a new output feature class.' It implies when to use the tool but does not explicitly state when not to use or mention alternatives, though the sibling list shows related tools like summarise_within and intersect_features.

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