Air list devices

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

No annotations are provided, so the description bears the full burden. It discloses that the operation lists devices (read behavior) and mentions authentication requirements for AirThings. However, it does not mention behaviors like pagination, rate limits, or what happens when no devices exist.

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 concise sentences with the purpose front-loaded. No redundant information, every sentence adds value.

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 tool with one optional parameter and no output schema, the description provides sufficient context: purpose, usage guidance, and a behavioral note about authentication for AirThings. It could mention other providers' requirements but is largely 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 schema has 0% description coverage, so the description must compensate. It implicitly adds meaning to the 'provider' parameter by mentioning AirThings support and the alternative for AirGradient. However, it does not explain the other enum values beyond that.

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 'Lists devices owned by the configured provider account,' which is a specific verb (lists) and resource (devices). It also differentiates from the sibling tool 'air_search_public_sensors' for AirGradient owned sensors.

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 tells when to use an alternative: 'For AirGradient owned sensors use air_search_public_sensors instead.' It also provides context about version support for AirThings. However, it does not fully clarify usage for other providers in the enum.

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