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

No annotations are provided, so the description carries the full behavioral burden. It discloses the report's contents and hints at a paid/professional ('PRO') gated service, but does not explicitly state that the operation is read-only, that an access token is required, or anything about rate limits, pagination, or response format.

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 a single front-loaded sentence with no wasted clauses. The only mildly non-essential element is the leading 'PRO.' tag, but it still efficiently conveys scope, contents, and intended audience.

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 annotations, no output schema, and two parameters, the description should carry more context. It reasonably covers scope and output categories, but it leaves the read-only nature, token requirement, ZIP format, and output shape to inference.

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 50%: access_token is documented in the schema, while zip is not described there. The description makes the zip parameter's purpose obvious ('for a ZIP') but does not specify expected format or constraints, so it adds some but not full semantic coverage for the undocumented parameter.

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 names a specific resource—an environmental due-diligence report for a ZIP—and enumerates its contents (facilities, violators, penalties). It implies an area-level report rather than a single-facility lookup, but never explicitly contrasts itself with the sibling tools epa_check or facility_search.

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?

It gives audience-oriented context ('for property buyers, lenders and site selection'), which implies when the tool is useful. However, it gives no explicit when-to-use versus epa_check and facility_search guidance and no exclusions or prerequisites beyond the schema-embedded token field.

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