The two tools have mostly clear boundaries: psbt_check initiates a PSBT inspection and may return a result when auto-paid, while psbt_check_result retrieves the result after invoice payment. There is minor overlap because psbt_check can also return a completed result, so the agent must understand the payment-state flow.

Both names are snake_case and share the psbt_check prefix, with psbt_check_result predictably indicating the follow-up result-retrieval operation. The naming is consistent and readable.

Two tools is minimal but justified for a single-purpose paid PSBT-check workflow: one initiates the check and one retrieves the paid result. The count is slightly thin but not inappropriate for this narrow domain.

The surface covers the full intended lifecycle: initiate a PSBT check, handle payment-required status, and retrieve the result via check_id. It also clearly states it never signs or sends, so no signing/sending tools are expected.