Delete Field Group

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is partly covered. The description adds genuinely new behavioral context: it verifies the field group is absent after deletion and imposes authorization gating (double gate, exact target echo, fixed confirmation phrase). That is meaningful disclosure beyond the structured hints, though it omits failure/rollback behavior.

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?

A single front-loaded sentence that opens with the core action and then appends the safeguards, with no wasted words. It is dense but every clause adds information.

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?

Because an output schema exists, return values need not be explained, and the destructive/idempotent hints are covered by annotations. The description adds the post-condition and gating requirements, but for a four-parameter destructive tool with zero schema coverage it still leaves parameter formats under-specified.

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 carries the full burden. It obliquely alludes to two parameters ('目标精确回显' for expected_dataset and '固定确认短语' for confirmation) but does not explain dataset_path or field_group_name and gives no format, syntax, or example for the confirmation phrase or echo matching. This leaves half the parameters undocumented.

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?

States a specific verb+resource ('删除精确字段组' / delete exact field group) plus a post-condition ('核验不存在' / verify non-existence), which clearly distinguishes it from siblings like arcgis_pro_list_field_groups and arcgis_pro_create_field_group. It is clear but does not explicitly name those siblings to differentiate further.

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 invocation prerequisites ('方案变更双门' / schema-change double gate, exact target echo, fixed confirmation phrase), which is implied usage guidance for a guarded destructive operation. However, it never says when to prefer this tool over alternatives such as arcgis_pro_gp_delete_field or arcgis_pro_gp_delete_dataset, so routing remains inferential.

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