The Cafe AURA MCP server defines 8 tools with mixed quality. All tools have descriptions and input schemas are partially present with Zod types. However, descriptions vary significantly in detail and some lack crucial guidance. Parameter descriptions are inconsistent, some tools have rich, detailed descriptions (e.g., make_reservation with specific constraints and prerequisites), while others are terse (e.g., get_cafe_info and get_wifi_info have zero-parameter tools with no input guidance needed, but missing output schema documentation). Schema validation uses Zod effectively, but output schemas are never explicitly documented, LLMs cannot plan downstream calls without knowing what fields will be returned. Error handling is minimal; tools return JSON but lack actionable recovery guidance. The server targets a specific domain (cafe management) with realistic workflows (search → availability → reserve → confirm), but tool composition lacks sufficient chaining metadata.

• Add explicit output schema documentation for all 8 tools. Example: get_cafe_info should document that it returns {hours: {open: string, close: string}, address: string, phone: string, seats: {indoor: number, outdoor: number}, ...}. This unblocks LLM planning and downstream tool calls.
• Enhance error messages with actionable recovery guidance. Example: get_reservation error should be 'Reservation AURA-20260303-001 not found. Check your confirmation email for the correct reservation ID, or call search_menu to start a new booking.'
• Add output field documentation to make_reservation showing the returned reservationId format (e.g., 'AURA-YYYYMMDD-NNN') so get_reservation and cancel_reservation calls are self-evident.
• Expand get_seat_availability description to explain: 'Returns available seat counts per time slot (indoor/outdoor) for the given date. If time is omitted, returns hourly availability summary (09:00-22:00). Use this before calling make_reservation to check capacity.'
• Convert inline parameter constraints to JSON Schema formal constraints. Add pattern: '^\d{4}-\d{2}-\d{2}$' and format: 'date' to date parameters; pattern: '^\d{2}:\d{2}$' to time parameters. This enables client-side validation and LLM self-correction.
• Add a confirmation pattern for cancel_reservation to prevent accidental cancellations. Either return a dry-run response first, or document that cancellations are irreversible and charged after 18:00 the prior day.
• Document parameter dependencies explicitly. E.g., in make_reservation note that 'seatType=indoor requires at least 1 available indoor seat; seatType=any falls back to outdoor if indoor is full.' Currently, these rules are hidden in implementation.