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

With no annotations, the description carries the full behavioral burden. It usefully discloses a limitation ('Does not give live flight status') and that fare data is current ('right now'), but says nothing about caching, freshness guarantees, or error behavior for unknown airports.

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 tight sentences with the scope and return contents front-loaded and the limitation placed last where it belongs. The airport enumeration is slightly long but serves as useful example data.

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?

There is no output schema, so the description correctly enumerates return fields and explicitly rules out live status. For a single-parameter lookup tool this is nearly complete, with the only gap being the accepted input format for 'airport'.

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 0% for the single required 'airport' parameter, so the description must compensate. It partially does by listing valid airport names (Allama Iqbal Lahore, Jinnah Karachi, Islamabad, etc.), but never states whether an IATA code, full name, or city is accepted, leaving the input format ambiguous.

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 names the specific resource (Pakistani airport details) and enumerates exactly what it returns: name, code, short description, and current cheapest flights. It also carves out a boundary by stating it does not provide live flight status, which separates it from status-oriented tools, though it never names a sibling alternative.

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?

Usage is implied rather than stated: an agent can infer it is for looking up an airport and seeing cheapest departing fares, but there is no explicit 'use this when...' guidance and no routing to siblings like cheapest_days, deals, or ticket_price when the user wants fares rather than airport data.

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