waysway

Most search and session tools are clearly distinct, but several boundary cases remain: update_user_profile and update_user_profile_from_model both mutate the same profile, ingest_user_message can also run fallback extraction, and get_booking_offers/check_stay_price overlap around post-search pricing. The detailed descriptions help resolve most ambiguity.

All tools consistently use snake_case verb_noun naming (search_hotels, update_stay_dates, get_session_state), and the verb set follows recognizable domain conventions. Minor differences like search_homestays_in_city vs search_restaurants_near_hotel do not break the overall pattern.

20 tools is at the heavy end for a single travel assistant, especially with debug/health/fallback tools such as health_check, list_sessions, and extract_user_profile_from_text padding the surface. It is still within a manageable range, but several tools could be consolidated.

The core hotel search/recommendation workflow is well covered (profile, dates, search, details, offers, price), but the broader travel domain is incomplete: homestays, activities, restaurants, and flight content only have search entry points with no details or booking step. There is also no reservation or confirmation operation even for hotels.