epa_toxic_releases

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful domain context about TRI and common sectors, but it does not disclose the return format, pagination behavior, time range, or data granularity, which would be valuable for an agent without an output schema.

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 four sentences with no filler, and the core purpose is front-loaded. Every sentence contributes: the purpose, the data source background, the common sectors, and the cross-reference guidance to sibling tools.

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 query tool with fully documented parameters and read-only annotations, the description is adequate. However, there is no output schema, and the description does not clarify what fields or structures the returned TRI data contains, leaving a meaningful gap for an agent deciding how to use the results.

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%: state, county, and rows each have clear descriptions with examples and defaults. The description's mention of 'by state' aligns with the required state parameter, but it adds no new meaning beyond what the input schema already documents for the parameters.

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 'Get Toxics Release Inventory (TRI) data by state', clearly stating a specific verb, resource, and scope. The second sentence explains what TRI tracks, which distinguishes it from sibling EPA tools like epa_facilities and epa_greenhouse_gas without needing to inspect their schemas.

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 gives clear context for when to use the tool: to retrieve TRI chemical release data by state. It also names alternative tools and their appropriate use cases ('Cross-reference with epa_facilities for compliance status and epa_greenhouse_gas for emissions'), but it does not explicitly state when *not* to use this tool or provide exclusion conditions.

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