Update your review of a lounge — change the rating and/or the text. Identify the review by lounge_slug.
| Name | Required | Description | Default |
|---|---|---|---|
| rating | No | New rating, 1-5 | |
| content | No | New review text (minimum 10 characters) | |
| lounge_slug | Yes | Lounge slug of the review to update |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description says 'Update your review' and 'change the rating and/or the text', which describes a mutating operation. However, the annotations declare readOnlyHint=true, directly contradicting the described behavior. This is a serious inconsistency that leaves the agent unsure whether state changes are actually made.
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 short sentences with no filler. The core operation is front-loaded, and the identification requirement is stated succinctly. Every word contributes useful information.
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?
The input schema provides complete parameter details for a small tool, but the description fails to cover essential context: whether an existing review must exist, what happens to the previous review text/rating, and especially why the readOnlyHint contradicts the update operation. The agent cannot form a safe, accurate mental model of the tool's effect.
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%, so the schema already documents lounge_slug, rating, and content. The description adds only the identification role of lounge_slug and the optionality of rating/text, which is minor; it does not materially improve on the schema.
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 and resource: 'Update your review of a lounge' and states the modifiable fields ('rating and/or the text'). It is clear that this tool modifies an existing review rather than listing or deleting it, but it does not explicitly name the sibling tools that create or delete reviews, so differentiation relies on inference.
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?
No guidance is given on when to use this tool versus alternatives such as lounge_write_review or lounge_delete_review. It implies the review already exists but never states prerequisites, nor does it mention that lounge_write_review should be used for new reviews.
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.
