Two tools with complete input schemas and basic descriptions, but significant gaps in parameter documentation and output schema clarity. Tool names follow verb_noun convention (airbnb_search, airbnb_listing_details). Descriptions are present but generic (avg 95 chars, below 194-char baseline). Most parameters lack descriptions, only 'location', 'id', and date fields have minimal text. No output schema documented. Error handling exists (robots.txt check) but lacks recovery guidance. No tool annotations (readOnlyHint, etc.). Composition is reasonable: two focused tools without overlap.

• Add descriptions to all parameters. Example: 'adults: Number of adult guests (1-16). Required if total guests > 0.' Format: 'param_name: What it controls (valid range/format). When required.'
• Document output schema in tool descriptions. Example: 'Returns array of listings with fields: id (string), title, price_per_night (number), rating (number 0-5), url (string), availability (boolean).'
• Add tool annotations to inputSchema: 'readOnlyHint: true' for both tools to signal idempotency and safety to agents.
• Enhance error messages with recovery steps. Instead of 'This path is disallowed by robots.txt', return: 'Airbnb blocks this search path. Try: (1) use --ignore-robots-txt flag, (2) narrow search with placeId, or (3) adjust date range.'
• Add min/max constraints to numeric parameters in schema. Example: 'adults: {type: number, minimum: 1, maximum: 16}' and 'minPrice: {type: number, minimum: 0, maximum: 100000}'.