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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered. The description adds that only *published* routes are returned, which is genuine scope information, but says nothing about pagination, result volume, or rate limits for what is framed as a complete enumeration.

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?

A single tight sentence with the resource front-loaded and a compact enumeration of what comes back. Nothing is wasted, though the field list brushes against what the output schema already provides.

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?

For a zero-required-parameter listing tool with an output schema present, the description is serviceable on returns. It omits filter semantics, unmapped parameter intent, and any comparison to the sibling tools, which leaves meaningful gaps for a 5-parameter discovery call.

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 only 40% and the description mentions no parameters at all — not q, market, airport, nor the two attribution fields. Worse, 'list every' implies no filtering is possible, which could steer an agent away from the very filters the schema exposes.

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 (List) plus resource (every published transfer route), and the enumeration of returned fields (route codes, airports, booking URLs) sharpens what kind of listing this is. It implicitly contrasts with the singular get_destination_details sibling but never names or distinguishes it explicitly.

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?

There is no when-to-use guidance, no statement of when to prefer this over get_destination_details, preview_transfer_quote, or list_markets, and no mention of the filtering parameters. 'List every published transfer route' implies a full-catalog browse but leaves the agent to infer how to narrow results.

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