Add Join

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=false, covering the safety profile. The description only adds generic boilerplate ('returns verifiable structured results; write and path restrictions subject to service capabilities') without stating permissions, reversibility, or what a join mutates in the project.

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?

It is short and front-loads the tool name, but the brevity reflects under-specification rather than efficiency. Both sentences are generic filler that could apply to any tool.

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 needn't be explained, but for a 6-required-parameter mutation tool with 0% schema coverage and no usage guidance, the description is far too thin to let an agent 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% across 7 parameters (6 required), so the description carries the full burden of explaining parameters like layer_field, join_field, and join_type. It mentions none of them, leaving field-matching and join-type semantics entirely undocumented.

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 says 'add add join', which essentially restates the tool name and title rather than explaining what a join operation does to a layer and table. It adds no differentiating detail from siblings like arcgis_pro_add_relate or arcgis_pro_remove_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?

There is no guidance on when to use this tool versus remove_join, add_relate, or gp_spatial_join. No prerequisites, context, or alternative-selection logic is provided.

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