Each tool has a distinct action scope: create, single-payment lookup by id, lookups by order reference, coin listing, pending listing, and refund listing. The three payment-reading tools (get_payment, get_payments_by_order, list_active_payments) are close in purpose, but the descriptions make the lookup key explicit enough that an agent can pick correctly.

All six tools follow a strict snake_case verb_noun pattern (create_checkout, get_payment, list_supported_coins, etc.) with consistent use of get_ for single lookups and list_ for collections. The only minor quirk is create_checkout naming the outcome 'checkout' rather than 'payment', which is still predictable and readable.

Six tools is tightly scoped to the payment-gateway domain: one create path, three read paths, and two reference-data/list tools. Nothing feels redundant or padded.

Core flow (create checkout, check status, track by order, list pending, list coins) is covered, but there is no way to create or cancel a refund or cancel a payment—only list_refunds exists. These are notable lifecycle gaps that would force an agent to fall back to the web dashboard.