Gp Erase

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, and openWorldHint=false, so the safety profile is partly covered. The description adds only generic claims about verifiable structured results and service-dependent write/path restrictions, without explaining what data is erased, overwrite behavior, or required permissions.

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 short but poorly structured and front-loaded with a malformed fragment ('erasegp erase'). The remaining clauses are generic boilerplate rather than useful, earned content.

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 a 3-required-parameter mutation-style geoprocessing tool with 0% schema description coverage, the description is completely inadequate. It does not explain the operation, parameter meanings, or usage context, despite having an output schema that could have freed it from explaining return values.

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 description provides no explanation of the three required parameters: in_features, erase_features, and out_feature_class. An agent gets no meaning beyond the bare parameter names already in the schema.

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 'erasegp erase', which essentially repeats the tool name and title without explaining the actual GIS erase operation. It does not distinguish this from sibling geoprocessing tools like clip, intersect, or union, leaving an agent unable to tell what this tool specifically does.

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 prerequisites, and no named alternatives such as arcgis_pro_gp_clip or arcgis_pro_gp_intersect. The sentence about write and path restrictions being subject to service capabilities is a generic caveat, not usage guidance.

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