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

With no annotations, the description carries the full burden of behavioral disclosure. It is quite transparent: it describes the return payload (FAA ground delays, arrival/departure delays, closure status, disruption score, traffic collapse detection) and the geographic scope. It lacks details on update frequency or potential error/empty-result behavior, but for a no-param read-only tool, this is adequate.

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 four sentences, each serving a distinct purpose: scope, return data, covered airports, and target users. There is no redundancy or filler. It is front-loaded with the core purpose and then provides necessary detail efficiently.

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 tool has no parameters, no output schema, and no annotations, the description must stand alone. It covers what the tool does, what data it returns, where it applies, and who uses it. This is a complete picture for a no-param data retrieval tool.

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 tool has zero parameters, so the baseline for this dimension is 4. The description does not need to clarify parameter semantics; the schema is trivial (empty properties). No additional parameter information could be added that would meaningfully improve the description.

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's function with a specific verb and resource: 'Get real-time air cargo disruption status at major US and international freight hub airports.' It lists the exact types of data returned (FAA delays, ground stops, etc.) and names key airports, making it easy to distinguish from sibling tools like rail or port status tools.

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: 'Used by air freight forwarders, express carriers, and logistics planners to reroute time-sensitive shipments around airport disruptions.' It implies that this is the go-to for air cargo disruptions, but it stops short of explicitly stating when NOT to use it or naming alternatives for other transport modes.

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