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

No annotations are provided, so the description carries the full burden. It discloses public-domain nature, pricing per row, return fields (handler, address, status, roles), and indicates it's a read operation. Does not discuss rate limits or authentication, but these are standard for public APIs. No contradictions.

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, front-loaded with a question, then capability, then return fields, then pricing. Every sentence adds value with no redundancy or fluff. Well-structured for quick understanding.

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 14 parameters, no output schema, and no annotations, the description covers all relevant aspects: what data is searched, filter options, return fields, and pricing. It also provides business context (EHS vendor universe). Pagination is implied via limit/offset parameters in schema. Complete for a search 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 100%, so baseline is 3. The description summarizes filter categories (company, state, etc.) but does not add significant new meaning beyond the schema parameter descriptions. The schema descriptions are adequate, so the tool description adds minimal extra value.

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 specific question, states the tool searches EPA RCRAInfo for registered hazardous-waste handlers, and distinguishes itself from ECHO by claiming it returns the entire regulated universe. The verb 'search' and resource are clear, and it differentiates from sibling tools like epa_tri_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?

The description implies usage when one needs RCRA handler data filtered by various criteria. It provides context (e.g., 'EHS vendor's entire regulated universe') but does not explicitly exclude other tools or provide when-not-to-use guidance. Lacks explicit alternatives naming.

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