Network Travel Modes

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that results include impedance, restriction, and hierarchy attributes, which is modestly useful context, but it says nothing about cost, network access requirements, or failure modes when the data source is invalid.

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 no filler; the verb and resource come first and the returned attributes are appended compactly. It is appropriately sized, though the terseness comes partly at the cost of the missing guidance noted elsewhere.

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-value documentation is not required, and the read-only annotation covers behavior. The remaining gap is the undocumented required parameter, which for a one-parameter tool is a meaningful omission.

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% for the single required parameter network_data_source, so the description must carry the burden and does not. It restates '网络数据源' without clarifying accepted formats (path, portal URL, network dataset name) or what happens with an unresolvable source.

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 (列出/list) and resource (网络数据源可用的 travel modes), and further specifies what is returned (阻抗、限制和层级属性). It is clear what the tool does, though it does not explicitly differentiate itself from network-related siblings like arcgis_pro_server_capabilities or arcgis_pro_na_* tools.

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 indication of when to call this tool, when not to, or what alternative to use for related questions. The agent must infer that this is a discovery/introspection step before network analysis, but nothing in the text says so.

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