Network Solve Od Cost Matrix

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

Annotations already state readOnlyHint=false, destructiveHint=false, openWorldHint=false, idempotentHint=false, so the agent knows this is a non-destructive local computation. The description usefully adds that solving happens locally against a NetworkDataset with no URL-service billing, but says nothing about output creation, permissions, or cost/limits.

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 key constraint (local NetworkDataset, no billable URL) comes first. It is efficient, though arguably too terse for a tool with this many required inputs.

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?

Output schema exists, so return values need no explanation, and annotations carry the safety profile. However, for an 18-parameter analysis tool with 0% schema coverage, the one-sentence description omits parameter meaning, prerequisites, and routing to alternatives, leaving the definition materially incomplete.

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 18 parameters, so the schema leaves origins, destinations, travel_mode, out_lines, barriers, units, cutoffs, etc. entirely undocumented. The description mentions only the NetworkDataset implicitly and adds no meaning for any parameter, leaving a huge compensation gap unfilled.

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 specific verb+resource: solve an Origin-Destination Cost Matrix using a local NetworkDataset. The clause '拒绝计费 URL 服务' hints at the distinction from URL/portal-based siblings (e.g. arcgis_pro_na_od_matrix), but it never names an alternative tool explicitly, so sibling differentiation is only implied.

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?

Implicitly says to use this when a local NetworkDataset is available and you want to avoid billable URL services. It gives no explicit when-to-use/when-not against the numerous network siblings, no prerequisites (network dataset must exist, travel mode must be valid), and no guidance on required vs optional workflow steps.

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