fa_get_airport_delays

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description's value is limited. It adds the behavioral trait 'current' implying real-time data, but does not disclose other traits like latency, rate limits, or response size. It does not contradict annotations.

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 highly concise at one sentence with a clear front-loaded purpose, no redundancy, and efficient use of words.

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 absence of an output schema and the tool's three parameters (including pagination), the description is insufficiently complete. It does not explain the return format, cursor usage, or max_pages behavior, leaving the agent underinformed for correct invocation.

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 coverage is 100% with all parameters described, so baseline is 3. The description adds extra value by explicitly highlighting the key 'id' parameter usage ('when `id` is given'), though it omits mention of 'cursor' and 'max_pages'.

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 retrieves 'current airport delays' and distinguishes two modes: all delays or a single airport when 'id' is provided. This specificity differentiates it from sibling tools like fa_get_airport (general info) or fa_get_airport_weather.

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 offers a basic usage condition ('or just one when `id` is given') but provides no explicit guidance on when not to use this tool or alternatives among the many sibling tools. The usage context is implied but not fully articulated.

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