Three tools with mixed quality. airbnb_search_agent has a complete schema with all parameters typed and described (location, checkin, checkout, adults with defaults). However, airbnb_search and airbnb_listing_details lack visible input schemas in the source code, only names and brief descriptions are shown. Descriptions are present but minimal (10-50 chars), below the 194-char baseline. No output schemas documented. No error handling guidance. Tool composition is reasonable (search → details), but parameter descriptions lack format constraints (date format stated in airbnb_search_agent but not enforced across tools).

• Add complete input schemas to airbnb_search and airbnb_listing_details in mcp.ts. Include parameter types (string, number), descriptions, and constraints (e.g., listing_id format).
• Expand tool descriptions to 100-200 chars. Example: 'Search for available Airbnb properties by location, check-in/out dates, and guest count. Returns a list of matching listings with price, rating, and availability. Call this first to discover properties, then use airbnb_listing_details for full information.'
• Document output schemas for all three tools. Specify: airbnb_search_agent returns string (agent response); airbnb_search returns array of {listing_id, title, price, rating, availability}; airbnb_listing_details returns {listing_id, description, amenities, reviews, host_info}.
• Add error handling guidance: 'If no properties found, suggest alternative dates or nearby locations. If listing_id is invalid, return available listing IDs from the last search.'
• Enforce date format validation in parameter descriptions: 'Check-in date in DD-MM-YYYY format, must be today or later. Example: 15-03-2025.'