ua12020010010037010

get_basic_profile ('basic administrative profile') and get_identity ('official name, code, type') overlap in scope and could be easily confused, as could get_sources vs get_basic_profile depending on interpretation. The remaining tools (council, hierarchy, welcome, search) have clearly distinct purposes.

Almost all tools use a consistent get_<noun> snake_case pattern (get_basic_profile, get_identity, get_regional_council, get_sources, get_territory_hierarchy, get_welcome). The single search_territory_knowledge breaks the pattern slightly but is still readable and idiomatic for a search action.

Seven tools is well-scoped for a read-only territory information server. Each tool appears to earn its place (identity, profile, council, sources, hierarchy, welcome, search), with no obvious filler.

The surface covers the expected read-only lifecycle for a territory info domain: identity, profile, administrative council, data sources, hierarchy, onboarding, and knowledge search. No create/update/delete is needed for static administrative data, so coverage looks essentially complete for the stated purpose.