Na Solve

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

Annotations already declare readOnlyHint=false, idempotentHint=false, destructiveHint=false, so the safety profile is known. The description adds only the generic boilerplate that write behavior and path restrictions depend on service capability, which is not actionable detail (no rate limits, no auth requirements, no statement of what state is changed). No contradiction with annotations.

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 short and front-loads the tool topic, but its brevity comes from under-specification rather than economy — the second clause is generic filler. It is not bloated, but it also does not earn its place with useful content.

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 an analysis-solving tool with a required layer parameter and an undocumented boolean, the description leaves the agent without the operation's semantics, preconditions, or parameter meaning. It is not complete enough to invoke this tool correctly with confidence.

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?

Both parameters (ignore_invalids, in_network_analysis_layer) have 0% schema description coverage and are never mentioned in the description, so the agent gets no meaning for them beyond their titles. Since there are parameters and coverage is low, the description should compensate but does not.

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 is essentially a restatement of the title and name ('求解na solve'), with no explanation of what a network analysis solve does or which analysis it performs. Among many siblings (na_create_route_layer, na_add_locations, na_service_area, na_od_matrix, network_solve_route), an agent cannot tell what this tool actually solves. No specific verb+resource meaning is conveyed beyond the tool name.

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 prerequisite (e.g., a layer created by na_create_route_layer must exist), and no reference to alternatives such as arcgis_pro_network_solve_route. The clause '写入和路径限制以服务能力为准' is a generic caveat, not selection guidance.

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