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

Annotations already declare readOnlyHint=true, so the description adds useful behavioral context: daily refresh, history to 2001, and the z-scoring methodology. It does not cover all possible behavioral aspects (e.g., rate limits, auth), but the added refresh cadence and historical depth go beyond the annotations, making this a 4.

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 a single well-structured paragraph that front-loads the core output, then lists returned fields, then provides use cases, and ends with update frequency. Every sentence adds value, and there is no redundant filler.

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?

The description explains what the tool returns (snapshot with trend, z_score, etc.), when to use it, and its data freshness and history. With no output schema, it does a good job describing the return values. It does not explain the 'days' parameter, but the schema does, so the description is nearly complete.

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?

The input schema has 100% description coverage for the only parameter ('days'), with a detailed explanation of its behavior. The description itself does not mention the parameter, but since the schema covers it fully, a baseline of 3 is appropriate.

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 returns a 0-100 US federal Clean Air Act enforcement-pressure score with specific methodology (EPA ECHO 90-day case velocity z-scored), and lists the fields returned (trend, z_score, etc.). It is specific and unambiguous, distinguishing it from the opaque sibling tool names.

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 explicitly says 'Call when the user asks about EPA air enforcement intensity, Clean Air Act compliance risk, or regulatory heat on manufacturers, utilities, or refiners, or when timing compliance spend, audit scheduling, or environmental-liability underwriting.' This provides clear context, but it does not mention when not to use it or name alternative tools, so it falls short of a 5.

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