Network Solve Closest Facility

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=false, so the safety and side-effect profile is partially covered. The description adds that it uses a local NetworkDataset, solves in one pass, and verifies explicit outputs, but does not clarify what gets written, what permissions are required, or how failures 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 a single front-loaded sentence with no filler or redundancy. It is concise and well-structured, though it is arguably too sparse for a tool with this many parameters.

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?

Given 21 parameters, 0% schema description coverage, and the presence of sibling network analysis tools, the description is inadequate. An output schema exists, so return values need not be explained, but input semantics, usage context, and behavioral details are largely missing.

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 21 parameters, so the description must carry the burden of explaining inputs. It only indirectly hints at network_data_source and the incidents/facilities concepts, without mapping any parameter names, defaults, or required formats.

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 analysis type: solve Closest Facility using a local NetworkDataset. It distinguishes itself from generic network solve siblings by naming the exact analysis, though it does not explicitly name alternatives.

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 using a local NetworkDataset and solving in one pass, which gives minimal context. However, it does not say when to use this tool versus siblings like arcgis_pro_network_solve_route, arcgis_pro_na_solve, or service area tools, and provides no exclusions or prerequisites.

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