epa_enforcement

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

The readOnlyHint annotation already establishes that this is a safe read operation, and the description adds context about case types and returned fields. However, it does not disclose pagination behavior, rate limits, data freshness, or any side effects, so it provides only moderate additional transparency beyond 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 4 sentences and front-loads the main purpose, with concrete return fields and case types. The cross-reference tip is somewhat tangential but adds useful direction without major bloat.

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 read-only search tool with well-documented parameters and a simple schema, the description covers the key aspects: purpose, case types, output fields, and related data sources. No output schema is present, but the description's list of returned fields compensates reasonably.

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?

All three parameters are fully described in the schema (100% coverage), so the baseline is 3. The description adds some context about case types but does not directly explain the law, state, or limit parameters beyond what the schema already provides.

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 clearly identifies the tool as searching EPA enforcement cases, specifying civil and criminal actions with penalties, settlements, and outcomes. It lists case types ('JDC' and 'AFR') and distinguishes it from sibling tools like epa_facilities or epa_toxic_releases, which focus on other EPA data.

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 provides no guidance on when to use this tool versus alternatives, and does not mention exclusions or prerequisites. It merely describes the tool's capabilities, leaving the agent to infer appropriate usage from the name and schema.

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