Gp Delete Features

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

Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=true, and openWorldHint=false, so the safety profile is covered. The description adds only a generic note that write/path restrictions depend on service capabilities, which is mildly useful but not operation-specific (no mention of what gets deleted, whether it can be undone, or permission 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?

Two short, front-loaded sentences with no padding; the operation is stated first. The second sentence is somewhat boilerplate but not wasteful enough to penalize heavily.

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?

For a destructive, 2-parameter mutation tool with 0% schema description coverage, the description leaves key gaps: what in_features accepts (layer, path, dataset), what expected_count does, and when this delete variant is appropriate. An output schema exists, so return values need not be described, but the invocation-side gaps remain.

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 explains neither parameter. "in_features" is semi-self-explanatory, but "expected_count" is completely unexplained — an agent cannot tell whether it is a validation guard, a batch limit, or something else.

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 states a specific verb and resource ("删除要素" / delete features), so an agent knows exactly what operation this performs. However, it offers no differentiation from nearby siblings such as arcgis_pro_da_delete_selected, arcgis_pro_da_delete_where, or arcgis_pro_gp_truncate_table, which all remove data in different scopes.

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 tool versus alternatives, no prerequisites, and no mention of the selection/where semantics that distinguish it from the other delete tools in the sibling list. The agent must infer usage entirely from the name.

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