Gp Eliminate

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

Annotations indicate write capabilities, idempotency, and non-destructive behavior, but the description adds no behavioral context. It does not explain what the tool does to features (e.g., eliminating small slivers by merging), nor does it disclose side effects or required conditions.

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 extremely short but fails to be informative. It is not concise in the sense of conveying necessary information efficiently; it is merely under-specified.

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?

Given six parameters, no schema descriptions, and a complex geoprocessing operation, the description is completely inadequate. It does not help an agent understand inputs, outputs, or behavior beyond what annotations loosely imply.

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%, so the description must compensate by explaining parameters like 'condition', 'part_area', 'part_option', and 'part_area_percent'. It provides no parameter information at all, leaving these completely 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 is essentially a restatement of the name: 'ArcGIS Pro: eliminategp eliminate.' This is a tautology and does not clarify that this geoprocessing tool merges selected polygon features into adjacent ones based on area/part conditions. No sibling differentiation is provided.

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 alternatives. The description does not mention prerequisites, typical use cases, or related tools.

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