kernel_density

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

With no annotations provided, the description must disclose behavioral traits. It only states the operation and a requirement. It does not mention that the tool creates a raster output, or any potential side effects such as overwriting files (despite an overwrite parameter). The description lacks transparency about the tool's behavior.

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?

The description is very concise, with two short sentences. No unnecessary words. However, it is so brief that it omits critical information. It achieves conciseness but at the cost of completeness.

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?

Given the complexity of kernel density estimation and the lack of annotations, the description is incomplete. It does not explain the output (e.g., a raster surface), how to interpret the results, or any units. The presence of an output schema (not shown) may mitigate this, but the description itself adds little context.

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?

The schema has a parameter descriptions coverage of 0% (per context). The description fails to explain any parameters, such as what 'cell_size', 'search_radius', or 'population_field' mean or how they affect the output. The agent must rely solely on the parameter names and default values, which is insufficient for a complex tool.

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 clearly states the tool creates a kernel density surface from points or lines, referencing the specific geoprocessing function (sa.KernelDensity). It succinctly identifies the resource and verb, distinguishing it from sibling tools that do not include density computation.

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?

The description mentions 'Requires Spatial Analyst' as a prerequisite but provides no guidance on when to use this tool versus alternatives (e.g., point density or line density). There is no discussion of appropriate contexts, data types, or exclusions.

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