Most tools have clearly distinct scopes: retrieval (query_memory, get_task_context, get_review_memory, get_session_handoff), writing (record_decision, record_review_outcome, summarize_to_obsidian), and session inspection (session_status, list_recent_sessions). There is some adjacency among the three retrieval tools and between session_status and get_session_handoff, but the descriptions give enough signals (citations/budget vs. raw memory vs. review findings vs. session handle) to pick correctly.

Predominantly consistent verb_noun snake_case (record_decision, query_memory, get_review_memory, check_decisions, list_recent_sessions). Minor deviations exist: session_status is a bare noun phrase with no verb, and summarize_to_obsidian adds a preposition plus a backend-specific name, which is less predictable than the rest.

Eleven tools is well within a healthy range and each maps to a concrete memory-lifecycle action (record, query, verify, share, summarize, handoff, inspect session). No redundant near-duplicates bloat the surface.

Core read/write paths for decisions, review evidence, sharing, summaries, and session handoff are covered. However, there is no explicit delete/forget/prune or supersede operation for a memory system where stale or private data must be removed, and check_decisions flags problems without any tool to resolve them, leaving dead ends.