mowteng

Tools are cleanly partitioned by engine via prefixes (bing_, gsc_, yandex_, indexnow_, insights_, mowteng_), so near-identical operations like submit_sitemap or submit_urls are clearly scoped to different targets. The few genuine overlaps — gsc_inspect_url vs insights_index_audit, gsc_performance_overview vs gsc_search_analytics vs the insights_* analyses — are explicitly cross-referenced in the descriptions (quota notes, 'insights_* tools compute common analyses over all rows'), which resolves most confusion though an agent may still hesitate on which analytics entry point to pick.

All names are snake_case and the overwhelming majority follow a predictable verb_noun pattern (list_sites, submit_sitemap, inspect_url, search_stats). Minor deviations are the engine-prefixed namespace tools (mowteng_routines, mowteng_sources) and the noun-only todo_list, which break the verb pattern but remain readable and clearly grouped.

31 tools is on the heavy side, but the surface spans three search engines plus IndexNow, cross-engine insights and scheduling helpers, so each cluster justifies itself. Still, there is visible duplication (three submit_sitemap variants, three list_sites variants, multiple analytics tools) that inflates the count beyond strict necessity.

The lifecycle is largely covered: site listing, sitemap list/submit (and delete for GSC), URL submission, index inspection/audit, performance analytics, cross-engine insights and daily task generation. Gaps are minor — Bing and Yandex sitemaps cannot be deleted, and there is no Bing/Yandex per-URL inspection — but these are workaroundable via IndexNow/GSC paths.