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

Annotations already declare readOnly, idempotent, non-destructive, open-world behavior, so the safety profile is covered. The description adds material context the annotations don't: the data source (EPA AQS) and the hard auth requirement ('Requires an EPA AQS email + key'). It stops short of describing pagination or rate-limit behavior beyond what the schema's limit field implies.

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?

Three sentences, well front-loaded: purpose first, then the routing use case, then sourcing/auth. Dense but nearly every clause earns its place. Minor redundancy in listing returned fields that overlap with the purpose statement.

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?

No output schema exists, and the description compensates by enumerating the returned monitor fields. Combined with the auth requirement and source disclosure, an agent has everything needed to select and call this tool correctly.

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 every parameter is already documented with geography modes, FIPS formats, date constraints, and the credential format. The description adds no parameter-level detail beyond the schema, so baseline 3 is correct.

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?

States a specific verb+resource ('EPA AQS monitor metadata for an area') and enumerates the returned dimensions: pollutants, agency, method, network membership (NCore/PAMS/SLAMS), objective, and open/close dates. It explicitly distinguishes itself from sibling aqs_sample_data by naming it, so the agent can route without opening either schema.

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?

Gives two concrete use cases — 'find the site codes aqs_sample_data needs' and 'check whether a place is monitored at all' — and names the sibling tool that consumes its output. The selection condition versus the alternative is explicit.

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