erase_features

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

No annotations present, so the description carries the full transparency burden. It discloses that the tool reads paths, writes output, and does not modify source datasets. This is valuable beyond the schema. However, it omits details like error behavior or workspace requirements.

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 three sentences, front-loaded with the core action. Every sentence adds value: purpose, use cases, and behavior. No wasted words, highly efficient.

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?

The description covers input, operation, and output, and notes non-destructive behavior. The presence of an output schema (per context) reduces the need to describe return values. It does not mention parameter constraints or overwrite handling, but these are in the schema. For a tool with nested parameters and multiple use cases, it is mostly complete.

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?

The input schema already provides detailed descriptions for all parameters, including path constraints and overwrite behavior. The tool description adds little new parameter-specific meaning beyond mentioning ArcPy Erase. Baseline 3 is appropriate given rich schema coverage.

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 action ('Remove portions of input features that overlap an erase layer using ArcPy Erase') and identifies the resource (features). It provides explicit use cases (exclusion zones, masking, subtraction), which helps distinguish from siblings like clip_raster or intersect_features.

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 lists explicit use cases but does not mention when not to use this tool or suggest alternatives. While the purpose is clear, lacking exclusions or comparisons to similar siblings slightly reduces guidance.

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