nas_status

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

With no annotations, the description carries the full burden, and it does disclose the output shape ('as points at the affected airport'), which tells the agent results are geolocated per airport. However, it says nothing about data freshness, whether it is a live snapshot versus historical, US-only coverage, or failure behavior when no ground stops are active.

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?

One compact sentence with the substantive content (event types) front-loaded and no filler. It is slightly clipped as a sentence fragment, but nothing is wasted.

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?

An output schema exists, so return values need not be explained, and the description covers the event-type scope and output geometry. It still leaves the 'detail' parameter unexplained and omits currency/coverage context that matters for a real-time aviation status feed with zero annotation coverage.

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 0% and the single 'detail' parameter (default 'short') is never mentioned in the description. The default value implies other modes exist, but the description gives no hint of valid values or what changes between them, so it fails to compensate 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?

Names a specific resource (FAA National Airspace System status) and enumerates the exact event types covered: ground stops, ground delays, arrival/departure delays, and airport closures. It is clearly not the same as aviation_sigmet or get_situation, but it never explicitly distinguishes itself from those aviation-adjacent siblings, and it uses a noun phrase rather than a verb.

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?

There is no statement of when to call this versus aviation_sigmet or any other aviation tool, and no prerequisites or exclusions. The agent must infer the usage scenario purely from the enumerated event types.

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