wx_taf

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It clearly communicates a read-only retrieval operation via 'Get' and 'Returns', and it enumerates the returned content (raw TAF, decoded periods with flight category, wind, visibility, ceiling). It does not mention edge cases like missing TAFs or units, but for a simple fetch tool this is reasonably transparent.

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 one sentence, front-loaded with the primary purpose, and every clause adds useful information about the returned data. There is no filler or repetition of the tool name.

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?

For a single-parameter forecast retrieval tool with no output schema, the description sufficiently covers the main return components. It does not specify handling of unavailable TAFs, time horizons, or units, but the core functionality is adequately described given the tool's simplicity.

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% for the single 'icao' parameter, which is already described as 'ICAO airport code'. The description does not add extra meaning about the expected format, examples, or ICAO rules, so it does not go beyond the schema. Baseline 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 'Get the Terminal Area Forecast (TAF) for an airport', identifying a specific verb and resource. It distinguishes itself from sibling weather tools by explicitly naming the TAF product, and the mention of 'raw TAF plus decoded forecast periods' offers a clear scope.

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 implies when to use the tool (when a Terminal Area Forecast is needed), but it does not explicitly state alternatives or exclusions such as 'for current conditions use wx_metar'. The usage context is inferable from the TAF name and the presence of weather siblings, but no direct guidance is given.

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