Gp Near

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

Annotations already establish idempotentHint=true, destructiveHint=false, and readOnlyHint=false. The description adds only 'returns verifiable structured results' and an opaque note that write/path restrictions depend on service capabilities, disclosing nothing about what output is produced or what the write behavior actually entails.

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?

It is short, but the brevity comes from under-specification rather than efficiency. The one substantive clause about service capabilities is boilerplate that does not earn its place.

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 the description still omits the tool's fundamental purpose and both parameter meanings. For a geoprocessing operation with two required inputs, this is inadequate.

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%, so both required parameters (in_features, near_features) are undocumented in the schema, and the description supplies no semantics for them either — not even that in_features is the source and near_features the reference dataset.

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 ('neargp near') without explaining what the Near geoprocessing tool does — that it computes distances/proximity from input features to near features. It never states a concrete verb+resource outcome, so an agent cannot distinguish it from dozens of sibling gp_* 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 when-to-use guidance, no mention of alternatives such as arcgis_pro_gp_generate_near_table or arcgis_pro_gp_spatial_join, and no preconditions. The vague 'per service capability' clause does not function as usage guidance.

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