search_epa_facilitiesSearch EPA-regulated facilities by state, ZIP, or SIC code. Returns facility name, address, compliance status, violations, and penalties.
| Name | Required | Description | Default |
|---|---|---|---|
| zip | No | 5-digit ZIP code | |
| limit | No | Max results (default 20) | |
| state | Yes | Two-letter state code (e.g., CA) | |
| sicCode | No | 4-digit SIC code to filter by industry |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=true and openWorldHint=true. The description adds that it returns specific fields (name, address, compliance status, etc.), but does not disclose behavioral traits like pagination or rate limits beyond what annotations provide.
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 two sentences, front-loading the purpose and listing return values. Every sentence is useful, 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 the 4 parameters, no output schema, and good annotations, the description adequately covers the tool's purpose and output. It explains return fields but could briefly note that results are a list with pagination hinted by the limit parameter.
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 the schema already documents each parameter. The description mentions state, ZIP, and SIC code but not limit, adding minimal extra meaning beyond the schema.
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 uses a specific verb ('Search') and resource ('EPA-regulated facilities') and lists search criteria (state, ZIP, SIC code), clearly distinguishing it from sibling tools like search_fdic_institutions or search_crime_statistics.
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 by stating what it searches, but it does not provide explicit guidance on when to use this tool vs alternatives, nor does it mention when not to use it.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool has a clear, specific purpose with detailed descriptions that differentiate them. Prefix patterns like get_district_, search_, analyze_, get_, etc., help an agent easily identify the correct tool for a task.
All tool names use a consistent verb_noun or verb_noun_noun pattern with underscores. The naming convention is uniform across the entire set, with no mixing of styles or ambiguous verbs.
With 47 tools, the count is high but justified by the broad scope of civic data analysis. While some agents might find the sheer number overwhelming, the tools are organized into clear categories (district profiles, searches, analyses) that make navigation feasible.
The toolset covers an impressively wide range of domains: legislation, representatives, districts, voting, committees, campaign finance, lobbying, federal spending, regulations, environment, energy, healthcare, housing, disaster, banking, consumer complaints, crime, vehicles, and more. There are no obvious missing operations for a civic data platform.