eliminate_polygon_part

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

The description explicitly states the tool is read-only on the source dataset: 'Reads in_features and writes out_features without modifying the source dataset.' This is a key behavioral trait. However, since no annotations are provided, the description carries full burden; it could disclose more (e.g., license requirements, performance implications), but the current disclosure is adequate.

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 concise: two sentences, front-loaded with the core action and use case. No extraneous information, every sentence serves a purpose.

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 (one nested parameter object with multiple sub-parameters) and the presence of an output schema, the description sufficiently covers the tool's purpose and key behavioral aspect (non-destructive). It could mention output feature class properties, but the output schema likely covers that. Overall, it provides enough context for an agent to select and invoke the tool correctly.

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 description only mentions in_features and out_features in passing, without detailing parameter semantics. However, the input schema itself provides thorough descriptions for each parameter (e.g., condition, overwrite, part_area, etc.). Since schema descriptions are rich, the description's minimal contribution is acceptable, but it does not compensate for the 0% schema description coverage as per guidelines.

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?

Description clearly states the tool removes small polygon holes/parts using ArcPy EliminatePolygonPart and writes output. It identifies the use case: cartographic cleanup, sliver removal, polygon interior simplification. However, it does not explicitly differentiate from sibling tools like simplify_features or multipart_to_singlepart, which are related but distinct operations.

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 clear use contexts: 'cartographic cleanup, removing sliver holes, or simplifying polygon interiors by area or percentage thresholds.' It implicitly advises when to use this tool, but does not mention when not to use it or suggest alternative tools.

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