notam-brief

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

With no annotations, the description carries the full burden, and it does disclose meaningful traits: the operation is a GET read, results are active notices with effective dates in both plain text and ICAO format, and access is metered ($0.020 per call, x402/USDC). It omits rate limits, cache/freshness, and error behavior, but the payment and read semantics are well covered.

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?

Front-loaded with the core purpose and resource, then example, then usage routing, then price — a sensible order with no wasted preamble. It repeats the FAA/US-airport framing twice ('official FAA NOTAMs' in both the opening and the Usage line), which is mild 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?

There is no output schema, so the description must describe returns, and it does (active notices, effective dates, plain text plus ICAO format). Combined with the disclosed payment model and the alternative-tool pointer, an agent has enough to invoke and interpret it, though freshness and failure behavior are unstated.

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%, so the baseline is 3. The description adds only an example call (GET ?location=KDFW) and confirms location is a US airport code; it says nothing about the 'notams' and 'critical' fields visible in the schema, so it neither compensates for nor deepens parameter meaning.

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?

States a specific verb+resource (retrieves official FAA NOTAMs for any US airport) and names the distinguishing scope (US airport codes, active notices with effective dates). It also explicitly routes the radius-search case to 'notam-area', so the agent can separate it from the other aviation tool without opening a schema.

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?

Explicitly says to use this for official FAA NOTAMs by US airport code (KDFW...) and points to notam-area via xynaptic-catalog for radius searches around any point. This gives both a use case and an alternative, though the indirect routing through the catalog tool is slightly awkward rather than a clean sibling pointer.

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