repair_geometry

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 that the tool rewrites geometry in place, may delete null geometries, and requires confirm=true. It lacks details on permissions or performance, but covers key destructive behaviors.

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 two concise sentences, front-loaded with purpose and usage, followed by a behavioral caveat. Every sentence adds value with no fluff.

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 the tool's complexity and lack of annotations, the description is mostly complete: it covers purpose, usage, and key behavior. It assumes knowledge of invalid geometry definitions and prerequisites but is adequate for typical use. An output schema exists so return values need not be explained.

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. It only adds that confirm=true is required, which is already in the schema. The description does not address delete_null or in_features beyond the schema, which already has good descriptions. Thus, it adds minimal value.

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 tool repairs invalid feature geometry using ArcPy RepairGeometry, and distinguishes from sibling tools like check_geometry by specifying it is used after checking for problems or before operations requiring valid shapes.

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 explicit usage context: use after check_geometry or before overlay/topology/network/export operations. It implies when not to use (if no geometry problems) and references a sibling tool (check_geometry) as prerequisite.

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