Validate Utility Network Topology

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is largely covered. The description adds that a write gate is required and references target identity echo, but it does not explain what validation changes, what errors it may produce, or how dirty areas are handled.

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 very short and front-loads the purpose before the prerequisite clause. It is not verbose, though the second clause is cryptic enough that its brevity may not fully earn its place.

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 7-parameter tool with 0% schema description coverage, the description omits nearly all parameter meaning and gives little usage context. The output schema exists, so return values need not be explained, but the input-side guidance is severely incomplete.

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 schema has 7 parameters with 0% description coverage, and the description names none of them. It does not explain aprx_path, map_name, source_kind, source_identifier, expected_network, extent, or extent_keyword, so it fails to compensate for the schema gap.

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: it validates Utility Network dirty areas. This distinguishes it from the generic sibling arcgis_pro_validate_topology, though the wording is terse and the second clause adds no purpose detail.

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?

It mentions a prerequisite ('需要企业写门' — requires enterprise write gate) but gives no explicit when-to-use, when-not-to-use, or alternative tools. The agent is left to infer when this validation should be run versus arcgis_pro_validate_topology or arcgis_pro_utility_network_trace.

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