faa_taf

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

The readOnlyHint annotation already establishes this as a safe read operation. The description goes beyond this by revealing the response structure (forecast periods with conditions, wind, visibility, clouds) and the station ID rule, adding useful behavioral context without contradicting the annotation.

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 three concise sentences, each with a distinct purpose: what the tool does, what it returns, and how to specify stations. It is front-loaded with the core purpose and contains no redundant or filler content.

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 read-only tool with no output schema, the description is fully sufficient. It tells the agent what data to expect (forecast periods with conditions, wind, visibility, clouds) and how to construct the request (ICAO codes, comma-separated). The readOnlyHint and schema round out the context.

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 schema fully describes the 'ids' parameter including ICAO code format and comma-separated multiple stations, so schema coverage is 100%. The description's mention of ICAO codes and comma-separation essentially mirrors the schema, providing no additional parameter meaning beyond the baseline.

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 action ('Get TAF') and resource ('for airports'), and specifies the key content returned (forecast periods with conditions, wind, visibility, clouds). It distinguishes itself from sibling weather tools like METAR or SIGMET by explicitly naming the TAF product, even though it doesn't mention alternatives by name.

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 provides clear context for when to use this tool: when TAF forecasts are needed for specific airports identified by ICAO codes. It also explains station ID formatting and multi-station support, which guides correct invocation. However, it doesn't explicitly mention when not to use it or name alternatives like faa_metar.

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