Gp Kernel Density

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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description adds only a vague boilerplate note about write/path restrictions being service-dependent and a claim of 'verifiable structured results'; it never states that a raster dataset is created, whether existing output is overwritten, or what permissions are needed.

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 omission rather than economy: the two clauses are generic filler that could be pasted onto any of these GP tools. No sentence carries tool-specific information.

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?

For a five-parameter geoprocessing tool with 0% schema description coverage, the description should at minimum explain the required inputs and the raster output. It explains neither, leaving an agent unable to configure the tool correctly despite the presence of an output schema.

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 five parameters (in_features, population_field, out_raster, cell_size, search_radius), and the description supplies no parameter meaning whatsoever. Nothing tells the agent that population_field is a numeric field, that search_radius is in map units, or what cell_size expects.

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 ('kernelgp kernel density') without saying what a kernel-density computation does or what it produces. It does not distinguish this tool from the many sibling interpolation/analysis tools such as arcgis_pro_gp_point_density, idw, or kriging, so an agent gets no semantic signal beyond the identifier.

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 prerequisites, and no named alternative. The only adjacent statement, 'write and path restrictions are subject to service capabilities', is a generic caveat rather than guidance on selecting this tool over the other density/interpolation siblings.

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