US Government Open Data MCP

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 behavioral traits like the types of cases returned and cross-referencing capabilities, but it lacks details on permissions, rate limits, pagination, or error handling. The description adds some context but does not fully compensate for the absence of 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 appropriately sized and front-loaded, starting with the core purpose. However, the second sentence about case types and the third about cross-referencing could be more tightly integrated. It avoids unnecessary repetition but has minor structural inefficiencies.

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 complexity (search tool with filtering), no annotations, and no output schema, the description is moderately complete. It covers the purpose, case types, and cross-referencing, but lacks details on output format, error cases, or behavioral constraints. It is adequate but has clear gaps for a tool with no structured output information.

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 all parameters (state, law, limit). The description does not add any parameter-specific semantics beyond what the schema provides, such as explaining interactions between parameters or default behaviors. The baseline score of 3 is appropriate given the high schema coverage.

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 states the tool's purpose with specific verbs ('Search EPA enforcement cases') and resources ('civil and criminal actions with penalties, settlements, and outcomes'). It distinguishes itself from sibling tools by focusing on EPA enforcement data, unlike the many BEA, BLS, CDC, and other agency-specific tools in the sibling list.

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 context by mentioning case types ('JDC', 'AFR') and cross-referencing suggestions (DOJ press releases, SEC financials, etc.), but it does not explicitly state when to use this tool versus alternatives. No explicit 'when-not' guidance or named alternative tools are provided.

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