The four tools have mostly distinct purposes: creating/reading the baton, rehydrating source, and running guard checks. There is minor overlap because vicem_read_baton checks git HEAD drift while vicem_check_guard also verifies staleness drift, but the descriptions clarify the different scopes.

All tools use a consistent vicem_ prefix and mostly follow a verb_noun pattern: create_baton, read_baton, check_guard. vicem_rehydrate is verb-only, which is a minor deviation but still clear and readable.

Four tools are well-scoped for the server's purpose of managing compressed context batons and code skeletons. Each tool earns its place without feeling thin or bloated.

The surface covers the core lifecycle: creating and reading the baton, restoring skeletonized source, and checking guards. Minor gaps exist, such as no explicit delete/clear baton or list ledger entries operation, but agents can likely work around these.