Most tools have clearly distinct purposes: route invocation (artex_call), discovery (artex_find_routes), event streaming (artex_read_events), browser automation (artex_browser), and status. The only mild overlaps are artex_initialize vs artex_login (both establish a session) and artex_change_password vs artex_configure_basic_auth (both rotate credentials), but the descriptions make the distinction between first-run setup, normal login, app password, and HTTP Basic gate explicit.

All ten tools share a consistent artex_ prefix and snake_case, and most use a verb_noun shape (find_routes, read_events, change_password, configure_basic_auth). Minor deviations are noun-only names (artex_browser, artex_status) and bare verbs (artex_call, artex_login), but the pattern remains predictable.

Ten tools is well within the ideal range and each earns its place: session lifecycle, credential rotation, route discovery/invocation, event streaming, browser automation, and health check. There is no filler or redundant surface for what is essentially a generic web gateway.

The surface covers the full session and credential lifecycle (initialize, login, logout, change password, basic-auth config) plus discovery, invocation, streaming, and browser inspection, so an agent is unlikely to hit a dead end. Minor gaps remain: no explicit route-listing beyond search terms, and no direct tooling for managing files in the transfer directory (only referenced indirectly via save_as/upload_files).