Gp Union

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=false, covering the safety and repeatability profile. The description adds only a vague note that 'write and path restrictions depend on service capabilities' and that results are 'verifiable structured' – neither is concrete. It does not contradict the annotations, but it adds little substance.

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 identity, but the brevity comes at the cost of substance rather than from trimming redundancy. Two clauses carry almost no actionable information.

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 explained, but for a geoprocessing write operation with two undocumented required parameters and zero schema coverage, the description omits nearly everything an agent needs: input requirements, output behavior, and overwrite semantics.

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% and there are two required parameters (in_feature_paths, out_feature_class). The description provides no information about input path format, whether multiple inputs are supported/required, or that out_feature_class is a write target. With no schema help, the description fails to compensate.

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 essentially restates the tool name ('uniongp union') without stating what a union operation actually does (combining polygon/feature geometries into a single output preserving overlapping areas). An agent cannot distinguish this from siblings like gp_intersect, gp_erase, or gp_symmetrical_difference on the strength of the description alone.

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 when-to-use guidance, no mention of prerequisites (e.g. polygon-only inputs), and no routing to alternatives among the many overlapping GP analysis siblings. The only forward-looking clause, 'write and path restrictions depend on service capabilities', is a non-specific disclaimer rather than guidance.

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