Scored across 72 tools
Many tools are clearly differentiated (dom_* vs iframe_* vs shadow_*), but several clusters overlap: close_tab/close_page, cookies_get/cookie_list/cookie_get, key_press/press_keys/key_down/key_up, and pdf/page_pdf. The cross-references help, but an agent has to carefully parse the differences among 72 tools, and some boundaries are genuinely unclear.
The wavexis_ prefix and snake_case run throughout, and groups like dom_*, iframe_*, and shadow_* are consistent. However, conventions are mixed across the set: bare verbs (navigate, click, wait), noun_verb (cookies_get, dom_get), verb_noun (list_tabs, set_files), and odd pairs like key_press/press_keys and cookie_list/cookies_get.
72 tools is far beyond the typical well-scoped 3–15 range and falls into the extreme category. Even for a broad browser automation server, this many entry points creates meaningful selection overhead and redundancy rather than earning each tool's place.
The surface covers the full browser lifecycle: sessions, tabs, navigation, DOM, iframes/shadow DOM, input, cookies, captures, and an invoke escape hatch for backend methods. It is hard to identify a significant missing operation for automation tasks.