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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered and the description need not repeat it. The description's one added behavioral fact is provenance — data comes 'from each airport's own pages' — which is useful but thin; nothing is said about coverage, freshness, or whether a single airport or many are returned.

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?

Two sentences, but the second is a comma-spliced list of eight topics that reads like a page blurb rather than a tool definition. Nothing is egregiously wasted, but the key fact (this returns airport ground-transport info for a given airport code) is buried behind the topic list.

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 read-only lookup with one fully documented parameter and no output schema, the description is roughly adequate: it hints at the subject matter of the returned content. It still omits the return shape (prose vs. structured fares), whether results span multiple airports, and behavior on unknown codes.

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% and the single 'code' parameter is documented in the schema with concrete examples (JFK, LAX, LHR, Heathrow). The description adds no syntax, aliasing, or matching-behavior detail beyond that, so the schema baseline of 3 applies.

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 first sentence just restates the title ("Getting a ride at an airport") and never states an explicit verb like 'returns' or 'looks up'. The second sentence does enumerate the content covered (pickup points, taxi rank, fares, charges, transport), which gives a rough sense of the payload, but it never distinguishes this from overlapping siblings such as get_taxi_tariff or check_fare.

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 guidance on when to call this versus alternatives, even though get_taxi_tariff, estimate_fare and check_fare overlap heavily on the fare/transport topic. No prerequisites, no exclusions, no mention of what happens for airports not covered.

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