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

Annotations already cover read-only and open-world behavior, but the description adds non-obvious operational context: quota consumption and a subscription-tier gate that would otherwise surface only as a runtime error. It stops short of noting rate limits or response shape, which is acceptable coverage.

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?

Two sentences, no waste, and the capability statement is front-loaded ahead of the cost/access caveats.

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?

Covers output nature (hourly AQI and pollutant values), horizon, cost, and access requirements with no output schema to lean on. Minor gaps remain: default value for 'hours' and whether location is resolved by coordinates only.

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 coverage is 67% with lat/lon documented but 'hours' carrying only min/max bounds. The phrase 'up to 72 hourly' effectively defines what 'hours' means (number of hourly forecast steps), compensating for the schema gap.

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 ('Read'), resource ('hourly AQI and pollutant forecasts'), and scope ('up to 72'). The forecast framing implicitly separates it from weatherbit_current_air_quality, though no sibling is named explicitly.

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 a prerequisite (air-quality API access on Business/Enterprise) and a cost note (consumes quota), which helps decide whether to call it. It does not say when to prefer this over weatherbit_current_air_quality or how to choose a horizon, leaving selection to inference.

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