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

Annotations declare readOnlyHint=true and openWorldHint=false, so the read-only nature is already known; the description adds meaningful context by explaining the score's composition and returned fields. It also notes the update cadence, though 'on source cadence' is vague and no rate limits or auth details are disclosed.

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 compact and front-loaded, leading with the verb, resource, and score range, then adding output fields, use cases, and freshness. Every sentence earns its place and there is no waste.

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 no output schema, the description compensates by listing return fields and the composite data layers, plus explicit usage contexts and update cadence. The optional parameter is fully covered by the schema, but a bit more detail on interpreting drivers or coverage would make it complete.

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 100%, with the `days` parameter fully documented: optional, returns daily history up to 5 years, and requires Gold tier. The description adds no parameter-level detail, so the baseline score of 3 is appropriate.

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 opens with a specific verb and resource: 'Returns a 0-100 county environmental burden score' backed by a composite of three ADW layers and named output fields. This clearly distinguishes the tool from the many sibling ADW packages by its environmental-burden domain.

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 explicitly states when to call the tool: 'when the user asks about pollution, regulated facilities, toxic releases, or environmental risk in a US county, or when timing site selection, underwriting, or due diligence.' It lacks explicit exclusions or named alternatives, so it stops short of the top tier.

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