Na Od Matrix

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=false. The description adds only a generic disclaimer ('write and path restrictions are subject to service capabilities') that is too abstract to be actionable - no mention of what gets created (an OD matrix layer), permissions required, or computational cost. It falls short of adding value beyond the 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?

Extremely short and front-loaded, but the brevity is under-specification rather than efficiency: two sentences that carry almost no information. Structurally acceptable, contentually thin.

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?

With an output schema present the description need not explain return values, but for a 5-parameter network analysis tool with 0% schema coverage and a non-readonly annotation profile, the description leaves the agent without the purpose, inputs, or prerequisites it needs. Only the safety annotations (present) keep this above 1.

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 5 parameters (network_data_source, travel_mode, cutoff, layer_name, number_of_destinations_to_find). The description contributes zero parameter meaning - no units for cutoff, no format for travel_mode, no explanation of what the output layer is named or where it lands.

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 essentially restates the tool name ('odna od matrix') with an 'ArcGIS Pro:' prefix. It never states a verb+resource ('compute an origin-destination cost matrix') or distinguishes it from the far clearer sibling arcgis_pro_network_solve_od_cost_matrix. A reader cannot tell what it actually produces from this text alone.

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, when-not-to-use, or alternative is given. The sibling arcgis_pro_network_solve_od_cost_matrix and arcgis_pro_na_solve are not referenced, so the agent gets no routing help. The only vague hint is 'write and path restrictions subject to service capability', which is not usage guidance.

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