Server exposes 7 tools with basic schemas and descriptions. All tools have non-empty descriptions (avg ~120 chars) and input schemas with type definitions. However, descriptions lack LLM-optimization guidance (no WHEN to use, no prerequisites, no recovery hints). Parameters are minimally described. Output schemas are not documented. Error handling is absent, no guidance on retryability, user-fixable vs fatal errors, or recovery paths. Tool composition is reasonable (single responsibility), but missing pagination for list_taxi_fleet and search_tour_packages. No tool annotations (readOnlyHint/destructiveHint). create_booking_enquiry is WRITE but lacks confirmation/dry-run pattern.

• Document output schemas for all 7 tools. Include field names, types, and descriptions. Example: get_business_info returns {business: {name: string, website: string, ...}, fleet: [{name, seats, rate_per_day_ac, ...}]}.
• Enhance descriptions with WHEN/WHY guidance. E.g., search_tour_packages: 'Use this to find packages by destination, duration, or theme. Call this first if you only have a destination name; use get_package_details if you already have a package_id.'
• Add tool annotations: mark all read-only tools with readOnlyHint=true; mark create_booking_enquiry with destructiveHint=true to signal it modifies state.
• Implement pagination for list_taxi_fleet and search_tour_packages: add limit (default 20, max 100) and offset parameters; return total_count and next_offset in response.
• Add error recovery hints to tool descriptions. E.g., get_route_info: 'If route not found, try search_tour_packages to discover valid destination pairs.' Include actionable error messages in responses (not just HTTP codes).