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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so safety is covered. The description adds data sources (FAA Class Airspace, UAS Facility Map, USGS elevation) and the exclusion of TFRs/NOTAMs, which is beyond the annotations and useful for setting expectations. No contradictions.

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 filler. The core purpose and output list are front-loaded, and the exclusion statement is concise. Every clause earns its place.

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?

There is no output schema, so the description carries the burden of explaining return values. It lists the airspace class, controlled airspace, LAANC ceiling (conditional), and the verdict. It also clarifies data sources and scope. It could mention error behavior for invalid inputs, but for the tool's complexity this 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?

Schema description coverage is 100%, so the parameters are already documented. The description only adds that zip uses the ZIP's center point, which is already in the schema. It does not add syntax, units, or interplay details beyond the schema, so a baseline 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 states a specific verb ('checks') and resource (US location) and enumerates exactly what is returned (airspace class, controlled airspace, LAANC ceiling, verdict). It clearly distinguishes itself from aviation siblings like decode_metar/decode_taf by focusing on airspace at a point, not weather or TAFs.

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 states what the tool does NOT cover ('not TFRs, NOTAMs or special-use airspace') and limits scope to one point. It implies usage for point-specific airspace checks, but does not explicitly name alternatives or say 'use this when X'. Still, the scope statement gives strong guidance.

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