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

Annotations already cover read/idempotent/openWorld, yet the description adds real behavioral context: invalid origin/dest codes are refused with a clear error ('never an empty success'), coverage is limited to recently loaded months, and it enumerates the returned metrics including per-cause delay breakdowns. This is exactly the value-add beyond structured fields.

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 scope, then systematically covers return fields, parameter behavior, coverage limits, and error handling. It is dense and long, but nearly every clause carries information; minor trimming of the verbose return-field enumeration would help.

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?

With no output schema, the description fully compensates by enumerating the returned metrics, disclosing the data-coverage window, and describing error behavior for unknown codes. An agent has everything needed to call and interpret this tool correctly.

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 schema already documents origin, dest, months (default 12), and carrier (code or common name). The description largely restates these same semantics, so the baseline 3 applies with no meaningful syntax or format addition beyond the schema.

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+scope: monthly on-time performance for ONE US domestic route (origin -> dest), with a named source (BTS TranStats). The 'one US domestic flight route' phrasing implicitly distinguishes it from carrier-level (carrier_ontime) and airport-level (bts_airport_delays) siblings.

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?

Explains the routing logic of the optional carrier parameter (pass it to scope to one airline; omit for all carriers) and a when-not caveat ('covers the most recent months loaded, not full history'). It stops short of explicitly naming alternative tools for carrier-level or airport-level queries.

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