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 ordering by handler-id, cursor pagination up to 1000/page, filters available, and that it is a standing roster without per-record registration dates. It also mentions pricing. However, it does not discuss authentication or rate limits, but these are less critical for a read-only feed.

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 dense paragraph, front-loaded with purpose. Every sentence adds value, including pricing. It is slightly long but efficient, with no wasted words.

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 no output schema, the description lists returned fields (facility, city, state, generator status, roles, NAICS), explains pagination and filters, and mentions pricing. It covers the essential context for a bulk feed tool, though a sample or field types could further improve completeness.

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?

The input schema has 100% description coverage for all 9 parameters. The description adds contextual grouping (e.g., filterable by state, generator status, NAICS, or flags) but does not provide additional meaning beyond the schema's individual parameter descriptions. According to guidelines, baseline is 3, so this is appropriate.

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 explicitly states it is a bulk feed of the full RCRAInfo handler roster, listing handlers in handler-id order with details like facility, city, state, generator status, roles, and NAICS. It distinguishes from the sibling epa_rcra_handlers_search by being a feed/paginated list versus a search 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?

The description clearly indicates this tool is for bulk retrieval of all handler records with cursor pagination and filtering options. While it does not explicitly state when not to use it or mention alternatives, the context and naming imply it is for comprehensive feed access vs. specific searches.

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