fa_get_airport_weather

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

Annotations already declare readOnlyHint and openWorldHint. The description adds only that it fetches weather, which aligns but does not disclose additional behaviors like pagination (cursor, max_pages) or response format. With annotations present, the bar is higher for adding context; the description adds minimal behavioral insight.

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 sentence, zero waste. Efficiently captures the tool's purpose without unnecessary detail.

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?

Given the absence of an output schema, the description fails to clarify the response structure or pagination behavior. It mentions data types but lacks completeness for a 4-parameter tool. Adequate but has clear gaps.

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%, with each parameter documented. The description adds little beyond the schema; it only reiterates the report enum values ('observations' vs 'forecast'). Baseline is 3 for high coverage, and no substantial extra meaning is provided.

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 the tool gets weather for an airport, specifying both current METAR observations and TAF forecast. It uses specific verbs and resources ('Get weather', 'METAR', 'TAF'), and distinguishes from sibling tools like fa_get_airport and fa_get_airport_delays.

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?

No explicit guidance on when to use this tool versus alternatives. While the description implies it is for weather data, it does not mention when to choose observations vs forecast, or when to use sibling tools like fa_get_airport_delays.

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