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

Annotations already cover safety (readOnly, idempotent, openWorld, non-destructive), and the description adds substantial meaning on top: scores are model estimates not safety ratings, 0-1 with 1.0 favorable, null means unscoreable, no_coverage marks placeholder numbers, caveats.<layer> carries limits, and it explicitly warns that absence of adverse signals is not a clean bill of health. It also discloses the geocoding source and per-layer geographic coverage.

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 opening sentence is well front-loaded with the layer list, but the remainder is one dense run-on paragraph mixing caveat semantics, coverage geography, and grid references. Much of it earns its place, yet the coverage enumeration is verbose and hard to scan for an agent deciding whether to call the tool.

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 no output schema, the description carries the full burden of explaining returns and does so thoroughly: value range, null vs no_coverage placeholders, caveats.<layer> structure, model-estimate provenance, and per-layer coverage. An agent has everything needed to interpret results correctly.

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 coverage is 100%, so the baseline is 3, and the description adds real value beyond it: it names the US Census geocoder used for addresses and clarifies that input is either an address or lat/lon coordinates. The lon sign caveat (negative except Guam, NMI, western Aleutians) largely duplicates the schema, but the geocoder detail is genuinely new.

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 states a specific resource (layer scores for a US location) and enumerates the exact layers returned (schools, hazards, groundwater, Superfund, air, noise, walkability, crime, climate), so an agent knows precisely what it gets. It does not, however, explicitly differentiate itself from the siblings broadband_availability, drinking_water, and environment_near, which overlap on environmental layers.

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 explicit when-to-use or when-not-to-use statement, and no sibling is named as an alternative. Usage is only implied through the extensive per-layer coverage list, which tells the agent where results will be real versus null/placeholder but leaves the routing decision to inference.

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