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

With no annotations provided, the description carries the full burden. It discloses the data is public-domain and self-reported, mentions pricing ($0.05/row), and implies read-only usage. It does not mention rate limits, authentication, or pagination behavior, but the nature of a search tool is reasonably clear. No contradiction with 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?

The description is packed into four sentences that are front-loaded with the core purpose, followed by detail on filters, output, and caveats. It is efficient but could potentially be tightened slightly without loss.

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 the lack of an output schema, the description adequately explains the return fields (facility, parent company, chemical, release totals) and provides pricing and source context. With 15 parameters, it covers the main usage scenarios. Minor omission: no mention of sorting or pagination behavior in the description, though those are in the schema.

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%, but the description adds context beyond parameter names: it explains that results are 'entity-resolved where possible', includes parent company and release totals, and notes that amounts are self-reported. This enhances understanding beyond the parameter descriptions alone.

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 starts with a clear question, specifies the EPA TRI Basic Data source, enumerates the many filter dimensions (facility, company, state, chemical, etc.), and states what is returned (facility, parent company, chemical, release totals). It thoroughly distinguishes this tool from sibling tools that cover other regulatory domains.

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 notes the tool is for 'environmental, remediation, and EHS sellers' but does not explicitly state when to use this tool versus siblings (e.g., epa_rcra_handlers_search). No when-not-to-use or alternative recommendations are provided.

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