Most tools are clearly distinct: search_events handles name/place/topic lookup, get_event_details handles a single occurrence, and the metadata tools (get_status, get_closures, get_registrations, get_recent_changes) each target a unique resource. The only mild overlap is the temporal-listing trio get_events (one day), get_week (one week), and get_events_range (arbitrary range), which an agent could plausibly confuse, though the descriptions make the granularity difference explicit.

All 11 tools use snake_case verb_noun form (get_events, list_program_types, search_events, refresh_now, etc.). The get_/list_/search_/refresh_ prefixes map predictably to retrieval vs enumeration vs query vs action.

Eleven tools is well within the sweet spot and each one covers a distinct retrieval shape (day, week, range, search, detail, metadata, maintenance). No tool feels redundant enough to remove.

The read surface is thorough for a scraped program-schedule domain: date-scoped listings, search, details, closures, registrations, change history, freshness status, and a manual refresh. Minor gaps remain — list_program_types returns categories with counts but there is no way to fetch events filtered by program type, and no venue/location listing tool.