Gp Repair Geometry

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

Annotations already declare idempotentHint=true and destructiveHint=false, but the description adds non-obvious behavior beyond them: it repairs in place (not to a new dataset) and uses a fixed KEEP_NULL mode that leaves null geometry records intact. That is genuine behavioral context an agent could not derive from the annotations or 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?

A single tight sentence, front-loading the mode and the in-place nature before the null-record caveat. No padding, though it is brief enough to leave obvious informational gaps.

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, and annotations cover safety. However, for a mutation tool with an undocumented required parameter and no sibling routing, the description leaves meaningful gaps around input expectations and when to prefer it over check_geometry.

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 the sole parameter in_features is documented nowhere. The description says nothing about what input features are accepted (layer vs. path, required state), so it does not compensate for the schema gap.

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?

States a specific verb+resource ('repair geometry') with the operational mode (in-place, KEEP_NULL) and a scope constraint (null geometries preserved). It does not name a sibling, so it lacks the explicit differentiation a 5 requires, but the purpose is unmistakable.

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 statement of when to use this versus related tools such as arcgis_pro_gp_check_geometry or arcgis_pro_gp_calculate_geometry, nor any prerequisites. Usage must be inferred from the name alone.

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