Air capabilities

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, which cover the operation's safety profile. The description adds context about listing configured providers via env vars, which gives a slight behavioral clue about data sourcing, but no additional behavioral traits beyond what annotations convey are disclosed.

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, near-emotional sentence that front-loads the verb 'Lists' and enumerates exactly what is returned. There is zero wasted wording, making it highly efficient and easy to parse.

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?

For a simple, read-only, optional-parameter inspection tool with a fully documented schema, the description is adequate. It covers the tool's purpose clearly. Minor gaps like explicitly stating that the operation requires no mandatory parameters or that it does not modify state are already implicit in the annotations and parameter count, so nothing critical is missing.

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 schema has 100% description coverage, including a clear explanation of the privacy_mode enum and its effect on output. The tool description itself does not add any parameter-specific meaning beyond the schema, which is sufficient; 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 lists supported providers, configured providers (via env vars), metrics, and privacy modes, which is a specific verb-resource combination. It distinguishes itself from siblings like air_current_reading or air_connection_status, which focus on current data or connection state, by indicating this is an enumeration/capability inspection tool.

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?

No explicit guidance is provided about when to use this tool versus alternatives. The description only states what it lists; it does not mention scenarios like 'to check available integrations' or 'when you need to see what providers are configured' or any exclusions. The agent is left to infer the intended context.

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