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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: data-source coverage limits per region and the fact that private-aircraft-only restrictions are specially labeled. No auth, rate-limit, or freshness details are given, but none are critical for a read-only snapshot.

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 content is front-loaded with the core purpose, then coverage caveats, then the exclusion. It is dense but each clause carries information; the parenthetical about private-aircraft labeling is slightly tucked away but 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?

With an output schema present, the description need not explain return values, and the annotations cover the safety profile. Combined with the coverage boundaries and the 'not for flight planning' exclusion, an agent has enough to call this correctly; only explicit routing to forecast/planning alternatives 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?

Schema description coverage is 100% and the single parameter already documents 'Airport code (IATA or ICAO)'. The description adds nothing about the parameter's format or edge cases, so this sits at the baseline for a fully documented schema.

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 names a specific resource (airport status) and enumerates the exact contents: FAA delays, ground stops, ground delay programs, closures, weather, and a delay-risk rating. It implicitly separates itself from siblings like get_airport_forecast by emphasizing 'right now'/'current', but it never names an alternative tool, so the sibling differentiation is inferred rather than stated.

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?

It gives clear exclusions ('Not for flight planning') and coverage boundaries ('FAA data covers U.S. airports; weather covers airports worldwide'), which tell the agent when this tool does and does not apply. It stops short of pointing at the correct alternative for forecasting or planning, which would be required for a 5.

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