List all lounge networks (Priority Pass, LoungeKey, DragonPass, Plaza Premium, Amex Centurion) with their descriptions and total lounge counts.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description says 'List all lounge networks,' a read-only operation, but the annotations include destructiveHint: true, which contradicts the stated behavior. This is an Annotation Contradiction. The annotation set is also internally inconsistent by pairing readOnlyHint: true with destructiveHint: true.
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, front-loaded sentence expresses the action, scope, and return contents with no filler. Every clause earns its place.
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 no-input listing tool, the description is largely complete: it names the output fields (descriptions and total lounge counts) and the domain (five named lounge networks). The destructiveHint contradiction introduces avoidable ambiguity, but the description itself provides the essential invocation and response context.
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?
The tool takes zero parameters, which sets a baseline of 4. There are no parameter gaps for the description to fill, and the description appropriately focuses on what the call returns.
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 uses a specific verb ('List all lounge networks') and names the exact networks covered, with their descriptions and counts. This clearly distinguishes it from sibling tools like lounge_get_network_lounges that operate on lounges within a network rather than the network catalog itself.
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?
The description offers no explicit when-to-use guidance and names no alternatives or exclusions. While 'List all' implies a broad catalog query, there is no contrast with lounge_get_network_lounges, lounge_find_lounges_by_access, or lounge_list_access_methods.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Several tools are near-duplicates (log_lounge_visit vs lounge_mark_lounge_visited, delete_lounge_visit vs lounge_delete_visit, audit_hotel_folio vs audit_marriott_folio) and the award-chart tools (get_pricing, get_program_rates, get_partner_award_options, get_program_partner_chart) have unclear boundaries. The three discover_more_flight_tools variants and overlapping lounge/portfolio listers compound the ambiguity, so an agent can easily pick the wrong one.
Most tools use snake_case verb_noun names and many have consistent prefixes (cards_, lounge_, fs_, sw_), but prefixes are applied inconsistently: log_lounge_visit/delete_lounge_visit sit outside the lounge_ prefix while equivalent lounge_* tools exist, and fs_search_flight references a non-existent search_flight. The broad get_/list_/search_ verbs are predictable, but the mixed domain-prefix style and duplicate concepts hurt coherence.
136 tools is far beyond a well-scoped server and bundles at least eight distinct domains (award search, cards, hotels, lounges, seatmaps, wifi, Viator, feedback). Many tools could be split into separate MCPs without loss of coherence, and the sheer count makes selection and prompt overhead prohibitive.
The core award-travel domain is well covered: bookings, hotels, points balances, statuses, vouchers, monitors, trips, and cards all have lifecycle CRUD, plus search and reference tools. Minor gaps exist (e.g. no true delete for standing orders, no single get for route monitors, and the Viator pair is an isolated mini-domain), but agents can generally complete workflows without dead ends.
