EPA Air Quality System (AQS) MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behavioral traits: it's a read-only health check (implied by 'Check if...is operational'), discloses authentication behavior ('Credentials are optional - uses environment variables as fallback'), and hints at response behavior ('verifies the API is responding'). It doesn't mention rate limits or detailed error handling, but covers essential operational aspects.

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 efficiently structured in two sentences: the first states the purpose and context, the second clarifies authentication behavior. Every sentence adds value without redundancy, and it's front-loaded with the core functionality. No wasted words or unnecessary details.

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 tool's low complexity (health check with 2 optional parameters), no annotations, and no output schema, the description is reasonably complete. It covers purpose, authentication behavior, and operational context. However, it lacks details on the return value (e.g., what 'operational' means in response format) and potential error scenarios, which would enhance completeness for an agent.

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 fully documents both parameters (email and key) as optional with fallback to environment variables. The description adds no additional parameter semantics beyond what's in the schema, such as format examples or edge cases. Baseline 3 is appropriate when the schema does all the work.

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 specific action ('Check if...is operational') and resource ('EPA Air Quality System (AQS) API'), distinguishing it from all sibling tools which focus on data retrieval rather than health checks. It explicitly identifies this as a 'health check endpoint' that 'verifies the API is responding,' making the purpose unambiguous and distinct.

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 clear context for when to use this tool ('Check if the EPA Air Quality System (AQS) API is operational'), implying it should be used for system status verification. However, it does not explicitly state when not to use it or name alternatives (e.g., other health checks or error-handling tools), which prevents a perfect score.

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