Each tool has a distinct role: search retrieves answer content, history audits revisions/tombstones, and status reports configuration. Search and history both perform temporal memory lookups, so an agent could occasionally confuse them, but the descriptions explicitly demarcate answer context versus audit data.

All three tools use the same memory_ prefix with a short noun-like suffix, giving a clear and predictable pattern. No mixing of conventions or verb styles.

Three tools is on the low side but each maps to a genuinely different capability (retrieve, audit, diagnose). The thinness is acceptable for a focused read-oriented memory interface, though it borders on under-scoped.

The surface is entirely read-only: there is no tool to store, update, or delete a memory, so the core write lifecycle of a personal memory system is absent. The mention of 'write availability' in status hints at writes happening elsewhere, which agents cannot invoke through this server.