Get your lounge reviews, including pending ones. Returns rating, content, approval status, and lounge info.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max reviews to return (default 20, max 50) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description accurately conveys a read-only 'Get' operation, but the annotations include destructiveHint=true, which directly contradicts the described behavior and readOnlyHint=true. This is a serious inconsistency that could mislead an agent into expecting side effects.
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 concise sentences front-load the core purpose and then enumerate the returned fields. There is no filler, and every sentence adds value.
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 read-only listing tool with one optional parameter and no output schema, the description covers the key return fields and the notable 'including pending ones' distinction. However, the destructiveHint contradiction undermines overall confidence in the tool's behavioral 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 only parameter, limit, is fully documented in the schema with its default and max. The description adds nothing about parameters, but schema coverage is 100%, so the baseline 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 description uses a specific verb ('Get') and resource ('your lounge reviews'), and explicitly notes it includes pending reviews. This clearly distinguishes it from sibling review tools like lounge_write_review, lounge_update_review, and lounge_delete_review.
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 phrase 'your lounge reviews' gives clear context that this is for retrieving the current user's own reviews, not those of others. It doesn't explicitly name alternatives or exclusions, but the read-vs-write/delete distinction from siblings is evident.
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.
