Each tool targets a clear resource+action pair, and the three page-mutation variants (page_edit for find/replace, page_update_section for heading-scoped replacement, page_append for end-of-page) are distinguished by explicit descriptions. Minor residual overlap between page_edit and page_update_section could still cause misselection in edge cases, and page_get vs table_get requires the agent to know whether it needs a table specifically.

Names follow a predictable resource_action pattern (page_get, table_update, issue_create, issue_transition) grouped by domain prefix. Small deviations exist: sites_list is plural where others are singular, and multi-word actions like page_update_section and table_add_row break the two-token rhythm slightly, but the convention remains readable.

19 tools serve two distinct product surfaces (Confluence pages/tables and Jira issues), so the count is roughly proportional to scope and each tool maps to a real operation. It sits near the upper end of comfortable, with the page-editing family being the only area that feels finer-grained than strictly necessary.

Both domains have near-full lifecycle coverage: pages support create/read/edit/append/delete/search/comment and issues support get/search/create/update/delete/transition/comment. Gaps are minor but present — no table row deletion or table creation, no page label or attachment operations, and no way to restore a trashed page.