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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds that results are exhaustive for the network and can be airport-scoped, but says nothing about result volume, ordering, or pagination for a potentially large worldwide list.

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?

Three tight sentences that lead with the core behavior and then explain the optional narrowing filter. No filler, no repetition, and the example usage is embedded efficiently.

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 simple, annotated read tool with no output schema and full parameter documentation, the description covers purpose, scope, and the optional filter adequately. The only shortfall is silence on result size or ordering for a network-wide list.

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%, with the network enum fully enumerated and the airport IATA pattern documented, so the baseline is 3. The description's examples largely restate what the schema already supplies, adding only the framing that airport narrows to a single airport.

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 and resource ('Get all lounges in a specific lounge network') and clarifies scope with concrete examples (all Priority Pass lounges worldwide). It does not name any sibling it competes with, so an agent must still infer the boundary against get_airport_lounges or search_lounges.

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?

Implies when the tool applies — retrieving everything that accepts a given membership, optionally narrowed by airport — and gives a worked example (Priority Pass at Heathrow). However, it never states when to prefer this over search_lounges, get_airport_lounges, or find_lounges_by_access, all of which are plausible alternatives in the sibling set.

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