Each tool targets a distinct stage of the card/delegation lifecycle, and gateway_delegate vs receipt_list are clearly separate concerns. The one soft overlap is card_build versus card_sign, since card_sign explicitly also builds the card, making card_build a strict subset step—descriptions disambiguate but an agent could reasonably pick the wrong one for a signed-card need.

All names follow a uniform snake_case noun_verb pattern (card_build, card_sign, card_verify, gateway_delegate, receipt_list). The subject-first convention is applied consistently across the whole surface with no style mixing.

Five tools is well-scoped for a narrow domain: card build/sign/verify, one delegation entry point, and one ledger read. Each tool maps to a real step in the pipeline with no filler or redundancy.

The core lifecycle (build → sign → verify → delegate → audit via receipts) is fully covered with no dead ends. Minor gaps remain: there is no tool to list/get existing cards from cards/, no key rotation or card revocation, and delegation is restricted to local test agents by design.