This server has significant definition quality gaps. Tool descriptions vary wildly in quality: search_available_future_listings is detailed (180+ chars), but most others are generic placeholders (10-30 chars like 'Get all details for a specific amenity by its ID'). 11 of 14 tools have minimal, non-actionable descriptions that fail to explain WHEN to use them or what distinguishes them from similar tools. Parameter descriptions are uniformly poor, most are auto-generated stubs ('The amenity_id parameter') with no context, format guidance, or constraints. No tool documents output schemas. No error handling guidance. No tool annotations. The server exposes get_database_url and test_database_connection, which are operational anti-patterns. Naming is mostly acceptable (verb_noun pattern), but several tools are near-duplicates (search_available_listings vs search_available_future_listings; get_listing_details vs get_featured_listings) without clear differentiation.

• Rewrite all 11 generic descriptions to 50-150 characters, answering: What does it do? When should the LLM call it instead of similar tools? Example: 'Get detailed information about a specific resort including amenities, location, and ratings. Use this after search_available_resorts to fetch full details before booking.'
• Replace all stub parameter descriptions with actionable text. For 'limit', write: 'Maximum number of results to return (1-100, default 20). Larger limits may slow response.' For 'check_in_date', write: 'Check-in date in YYYY-MM-DD format (e.g. 2025-06-15). Must be today or later.'
• Document output schema for each tool. Specify which fields are returned, their types, and which are safe to pass to downstream tools. Example: 'Returns array of {listing_id: int, resort_id: int, check_in: ISO8601, price_night: float, available: bool}.'
• Consolidate duplicate tools: merge search_available_listings and search_available_future_listings into one search_listings tool with a 'date_range' parameter (past|future|all). Merge get_featured_listings and get_weekend_listings into get_listings with a 'filter' enum (featured|weekend|all).
• Remove get_database_url and test_database_connection from the tool set. These are operational concerns, not agent-callable tools. Move diagnostics to server startup or a separate admin endpoint.