Fetch normalized public Airbnb room review snippets by room ID and page for guest feedback analysis.
Get Airbnb room reviews. Returns normalized Airbnb public review snippets.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Room id | |
| page | No | 1-based page |
Changes observed during successful MCP inspections.
v1.6.0v1.6.0v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Without annotations, the description only says 'Returns normalized Airbnb public review snippets.' It does not disclose pagination behavior, rate limits, or what 'normalized' entails. Minimal behavioral context.
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 sentences front-load the action and provide direct purpose. No extraneous 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?
Given no output schema, the description lacks detail about the structure of reviews (e.g., rating, text, date). The term 'normalized' hints but is incomplete. Adequate but not comprehensive.
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 coverage is 100%, so the schema already describes parameters (id, page). The description does not add meaning beyond what the schema provides, so 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 clearly states 'Get Airbnb room reviews' with a specific verb and resource, and distinguishes itself from sibling tools like 'airbnb_room' and 'airbnb_room_calendar' by focusing on reviews.
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 on when to use this tool versus alternatives like 'tripadvisor_reviews' or 'googleplay_reviews'. It does not mention prerequisites or context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.