Validate Topology

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

Annotations declare readOnlyHint=false, meaning this operation writes (typically flagging/refreshing topology errors and dirty areas), but the description never discloses what state changes occur or what must hold before running. It only notes the return of GP messages, which the output schema already covers.

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 compact sentence with the scope constraint front-loaded before the return value; nothing is wasted. It is terse to the point of under-specifying, but structure is sound.

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?

The output schema handles GP message returns, but for a non-read-only validation tool with two undocumented parameters, no usage routing, and no disclosure of side effects, the description leaves significant gaps an agent would need filled.

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 burden. It implies 'extent' is optional (full range when omitted), which is useful, but gives no format, coordinate-system, or syntax guidance for extent, and says nothing about the required topology_path.

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 ('validate topology') and names the scope (full extent or specified extent) plus the return type (GP messages). It is distinguishable from siblings like arcgis_pro_topology_info or arcgis_pro_create_topology, but never explicitly contrasts itself with them.

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 when-to-use guidance, no prerequisites, and no named alternative despite several closely related siblings (arcgis_pro_topology_info, arcgis_pro_export_topology_errors, arcgis_pro_validate_utility_network_topology). The agent must infer usage from the verb alone.

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