US EPA Compliance Check MCP

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.

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 cost (FREE) and that it returns a compliance summary (count, violators, top 3 worst), but omits data source/freshness, read-only/query nature, and any auth or rate-limit constraints.

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?

Very concise and front-loaded: pricing flag first, then scope and return summary in one sentence. No filler, and every phrase contributes to selection or expectation.

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?

For a one-parameter query with no output schema and no annotations, the description covers the resource, ZIP scope, and key return contents (count, violators, top 3 worst). It still lacks exact response-shape and data-freshness details, but is broadly sufficient for this simple tool.

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 0% and the only parameter is a raw string named zip. The description clarifies that this is a US ZIP code, adding meaning beyond the schema, but gives no format or validation details such as 5-digit ZIP expectations.

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 resource (EPA-regulated facilities) and scope (US ZIP code) plus a compliance status summary (count, violators, top 3 worst). This is clear and implies a different role from facility_search and area_report, but does not name or explicitly distinguish the siblings.

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 when-to-use, when-not-to-use, or alternative guidance. 'FREE' is pricing information rather than usage context, so the agent must infer that this is for ZIP-level compliance summaries versus facility lookup.

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

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 usefully indicates that results cover compliance, violations, inspections, and penalties, but it does not disclose matching behavior, result limits, pagination, or access requirements beyond the access_token schema note.

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 efficient sentence with the core search behavior front-loaded. The only minor ambiguity is the unexplained 'PRO.' prefix, but it does not waste space.

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?

For a simple three-parameter search with no output schema and no annotations, the description covers the core purpose and result domain but leaves important call details unspecified, such as state format, name-matching semantics, and result behavior.

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 only 33%, so the description must compensate. It does clarify that 'name' can be a company or facility name and that 'state' is optional, but it does not specify state format or whether name matching is exact versus partial.

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 verb and resource: search EPA facilities by company/facility name with optional state. It is clearly distinguishable from a generic check or area report, though it does not explicitly contrast itself with the sibling tools.

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 phrase 'by company/facility name (+ optional state)' implies when this tool is appropriate, but it gives no explicit guidance on when to use it instead of epa_check or area_report, and no exclusions or prerequisites are stated.

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