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

Annotations only declare readOnlyHint and openWorldHint; the description adds material context beyond them: an explicit price ($0.002 USDC per successful call), the payment rails (x402 on Base, Solana or Arc), and the failure semantics ('failed calls are not charged'). That payment/failure disclosure is exactly the kind of pre-invocation information an agent needs for a paid endpoint.

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?

It is a single dense paragraph, but it is front-loaded with what the tool returns before moving to scope, pagination and pricing. Every clause carries information (scope, cost, page size, disclaimer), though breaking the payment terms into their own sentence would read more cleanly.

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?

An output schema exists and return fields are listed anyway; coverage of scope, pagination depth is bounded by the page param, cost model, and the flight-planning disclaimer leaves nothing an agent needs before calling. Complete for a read-only, paid, paginated data feed.

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 three parameters (page, type, location) are already documented with examples, including the ICAO/FAA id formats. The description adds only the page-size detail ('30 NOTAMs per page') and example type values, which largely restate the schema, so 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 names a specific resource (Active FAA NOTAMs from FAA's public NOTAM Search) and enumerates the returned data: NOTAM number, type, effective/expiry times in UTC, ICAO and plain-language text, plus counts by type. The scope qualifier 'US (FAA) locations only' makes it unmistakable against any sibling tool, none of which cover NOTAMs.

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 gives a clear usage context plus a real exclusion ('not for flight planning') and a geographic restriction ('US (FAA) locations only'). It does not name an alternative tool or describe when a sibling would be better, so it stops short of full 5-level routing guidance.

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