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

The description adds value beyond the annotations by specifying the forecast period (24-30 hours), update cadence (4x daily), and content breakdown (6-hour windows). It does not contradict the readOnlyHint, destructiveHint, or idempotentHint annotations, and the openWorldHint aligns with the forecast nature.

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 description is concise (two sentences) with the essential information front-loaded: type of forecast, validity period, content, and update frequency. Every sentence adds value without redundancy.

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 presence of an output schema (true), the description does not need to detail return values. It sufficiently covers the what, when, and update frequency, making it complete for a forecast retrieval tool with good annotations.

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?

The single parameter (icao_codes) is fully described in the schema with examples, achieving 100% coverage. The description reiterates the parameter's purpose but does not add new semantic detail beyond what the schema provides. Baseline of 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 clearly states the tool provides TAF Terminal Aerodrome Forecasts for airports, specifying the time frame (24-30 hours) and included elements (wind, visibility, weather phenomena, sky conditions in 6-hour windows). This distinguishes it from sibling tools like aviation.metar.current or checkwx.taf.decoded.

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?

While the description clarifies the scope and update frequency, it does not explicitly guide the agent on when to use this tool versus alternatives like checkwx.taf.decoded or aviation.metar.current. The context of 24-30 hour forecasts implies usage for planning but lacks explicit when-to-use or when-not-to-use guidance.

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