Import Attribute Rules

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the mutation risk is known. The description adds meaningful non-redundant context: the double-gate schema-change protection, exact target echo, and fixed confirmation phrase, which materially shape how the agent must prepare the call.

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 dense sentence with the action front-loaded and the gating requirements trailing. It wastes few words, though the compressed jargon ('双门', '回显') reduces immediate readability.

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?

An output schema exists, so return values need no explanation. However, for a destructive 5-required-parameter operation with zero schema coverage, the description omits what dataset_path and csv_files expect (formats, directory semantics), leaving the agent under-informed before a mutating call.

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% across 5 required parameters, so the description must carry the load. It hints at expected_rule_names (核验预期名称集合), target (目标), and confirmation (固定确认短语), but leaves csv_files and dataset_path unexplained, so it only partially compensates.

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 (导入/import), resource (属性规则/attribute rules), and source (官方 CSV within INPUT_ROOTS), which cleanly distinguishes it from arcgis_pro_add_attribute_rule (single rule) and list/export siblings. The reference to 'INPUT_ROOTS' rather than a schema parameter name slightly blurs the picture.

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 conveys the operational prerequisites (schema-change double gate, exact target echo, fixed confirmation phrase) but gives no guidance on when to prefer this bulk import over arcgis_pro_add_attribute_rule or how it relates to the export sibling. Usage is implied rather than stated.

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