Network Solve Route

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

Annotations already declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the safety profile is covered. The description adds genuine context beyond them: the solver is not retained in-process, so results must be exported, which explains why out_routes/out_stops/out_directions are required. It does not cover overwrite/confirm_overwrite semantics or permission requirements.

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, front-loaded with the action and API, with no filler. It is efficient, though the brevity is partly achieved by omitting needed parameter detail rather than by editorial discipline.

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 not be described, but for a 13-parameter mutation tool with 0% schema coverage the description is far too thin. Key inputs and the overwrite-confirmation flow are unexplained, so an agent cannot call this correctly from the definition alone.

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 13 parameters, so the description must carry the burden. It only implicitly accounts for three output paths (Routes/Stops/Directions) and says nothing about stops, travel_mode, network_data_source, the three barrier inputs, overwrite, confirm_overwrite, or ignore_invalid_locations, leaving most inputs undocumented anywhere.

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 concrete verb+resource ('求解路线' / solve route) and names the underlying API (arcpy.nax) plus the artifacts produced (Routes/Stops/Directions). The phrase '一次性' and '不保留进程内 solver' implicitly distinguishes it from the multi-step layer-based siblings (arcgis_pro_na_create_route_layer / na_add_locations), though no sibling is named explicitly.

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?

'一次性求解' implies a one-shot workflow versus the incremental create-layer/add-locations/solve pattern, which is weak but real guidance. There is no explicit when-to-use, when-not-to-use, or prerequisite (network data source, travel mode availability) statement, and no sibling such as arcgis_pro_na_solve is named as an alternative.

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