Export Subnetwork

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

Annotations already cover the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=false). The description adds genuine behavioral detail beyond that: NO_ACKNOWLEDGE is fixed and existing output files will not be overwritten (so the tool errors rather than clobbering). However, it does not describe prerequisites (network topology state, permissions) or how failures surface, and the 'read-only' framing is scoped to the network rather than the file write.

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 front-loaded sentence with three useful clauses and no filler; every clause carries information. It is efficient and well-structured, though arguably undersized for a tool with ten 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?

An output schema exists, so return values need not be explained. But for a tool with 10 parameters and no schema descriptions, the description is far too sparse to let an agent construct a correct call. Key inputs and any prerequisites are undocumented, leaving significant gaps.

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 10 parameters (8 required) with 0% description coverage, so the description must carry the burden of explaining them. It does not: aprx_path, map_name, source_kind, source_identifier, domain_network, tier, subnetwork_name, output_json, include_geometry, and include_domain_descriptions are never explained or mapped. The agent gets no help understanding what these inputs mean or how they relate.

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: export the specified subnetwork to JSON. An agent can distinguish this from siblings such as arcgis_pro_update_subnetwork or arcgis_pro_utility_network_trace by the export action and subnetwork target. It stops short of explicitly naming sibling alternatives, so it is clear but not fully differentiated.

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?

No when-to-use or when-not-to-use guidance is given, and no alternatives are named. The only context is behavioral constraints (read-only, NO_ACKNOWLEDGE, no overwrite), which are not usage routing. An agent is left to infer when this tool is the right choice over the other subnetwork/network tools.

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