get_metar_taf

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

With no annotations, the description carries the full behavioral burden. It clearly discloses edge-case behavior (null for missing type, notFound list for absent IDs) and 'Fetch' implies a safe read operation. Omissions like auth or rate limits are less critical here, but explicit response structure is only hinted at.

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 deliver high informational density with the action and scope front-loaded. The second sentence efficiently covers edge cases without redundancy, making every word earn 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?

The tool lacks annotations and an output schema, so the description must provide more context. It covers the core purpose and edge cases but omits the reportTypes parameter behavior, the maxItems limit, and a fuller response structure. This leaves the agent with questions about optional configuration.

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%, so the description must compensate. It explains airportIds via 'ICAO airport identifiers' but does not mention reportTypes, which controls whether METAR, TAF, or both are returned. This is a meaningful gap for parameter understanding.

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 opens with 'Fetch decoded current METAR observations and TAF forecasts' which is a specific verb and precise resource, clearly distinguishing it from sibling tools like get_notams or get_airport_info. The added regulatory reference reinforces the purpose without ambiguity.

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 ties usage to the 14 CFR 91.103(a) preflight requirement, giving a clear context for when to invoke it. However, it stops short of naming alternatives or stating when not to use it, so it earns a 4 rather than a 5.

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