Noaa

Several tool clusters have unclear boundaries: ask_pipeworx, ask_pipeworx_beta, ask_pipeworx_grounded, and deep_research all route the same queries with only subtle behavioral differences, and ask_pipeworx_beta is explicitly stated to currently behave exactly like ask_pipeworx. The polymarket_* family also overlaps heavily (edges, edge_tracker, arbitrage, fill_risk), and ai_visibility_check vs scan_competitor_ai_presence add further confusion.

Tool names are overwhelmingly consistent snake_case with a verb-first pattern (ask_, compare_, resolve_, validate_, subscribe, recall, forget). Minor deviations exist, such as noun-first names like recent_alerts and recent_changes, and the polymarket_* group uses a noun-prefix scheme, but the overall pattern is predictable and readable.

At 31 tools, this exceeds the 25-tool threshold where the set starts to feel heavy, and many tools are near-duplicates or differ only by mode or depth. While the underlying data scope is broad, the exposed surface could be consolidated (e.g., folding ask_pipeworx_beta into ask_pipeworx and merging the polymarket edge tools).

The tool set covers its apparent domain thoroughly: universal lookups, grounded verification, entity resolution/profiles/comparisons, Polymarket analysis, subscriptions, and memory CRUD are all represented. A minor gap is the lack of a direct fetch-by-citation tool (e.g., resolving pipeworx:// URIs inside the tool surface), relying instead on resources.