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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive behavior. The description adds valuable behavior beyond that: the covered flag behavior outside pilot communities, data provenance (enviroatlas.epa.gov), and that no auth is required. No contradictions with the annotations.

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?

Three sentences, front-loaded with the core action, then an illustrative metric list, and finally the critical coverage caveat plus data source and auth note. Every sentence carries selection or invocation value; there is no filler.

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 an output schema present and annotations covering the safety profile, the description supplies the remaining needed context: coverage boundary, pointer to the community list, data provenance, and no-auth requirement. Nothing an agent needs to correctly invoke or interpret the result is missing.

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; the description adds a meaningful semantic constraint on lat/lon values by stating that points outside the 32 pilot communities return covered=false. This is information the schema's range checks do not convey.

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?

States a specific verb ('Get') and resource ('EPA EnviroAtlas ecosystem-service metrics') with a precise scope: 'census block group containing a lat/lon point.' The long illustrative list of metric categories further clarifies what the tool returns and helps distinguish it from the sibling community-level tool.

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?

Provides clear context: a point-based lookup against a block group, the coverage limitation to '32 EPA pilot communities,' and a pointer to 'enviroatlas.communities' for exploring coverage. It does not explicitly name an alternative like community_summary or state a when-not-to-use rule, so it falls short of a full exclusion-based guideline.

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