The two tools are perfectly complementary: cogvault_recall is read/search and cogvault_record is write/save. There is no overlap, and the descriptions make the read-before-write workflow explicit, so an agent can never confuse them.

Both names follow the same predictable pattern of a namespace prefix plus a clear verb (cogvault_recall, cogvault_record). This is a consistent, readable convention with no deviations.

Two tools is the bare minimum for a persistent memory store covering store and retrieve. It is borderline thin; a memory service realistically needs at least update/delete/forget to feel well-scoped.

The core save-and-search lifecycle is covered, but there is no way to update, correct, or delete a memory card once recorded, and no listing or browsing operation. These are notable gaps that could force agents to rely on superseding stale cards.