zsign

Most tools target a clearly distinct resource+action (send_envelope vs void_envelope vs remind_envelope vs get_envelope_status vs get_audit_trail). The main fuzziness is the three send paths (send_envelope, send_draft, send_from_template) and the balance-overlap between check_balance, get_account, and get_usage, but the descriptions explicitly delimit these cases.

Every tool follows a consistent snake_case verb_noun pattern (send_draft, get_signing_links, list_templates, download_certificate, void_envelope). Verbs are used consistently for the same kind of operation across the whole set.

29 tools is at the heavy end for a single server, partly driven by ancillary tools (buy_credits, check_balance, get_pricing, get_referral_link, get_usage). The e-signature domain is genuinely broad, so it is borderline rather than egregious, but some commercial/billing tools feel like they could be consolidated.

The full envelope lifecycle is covered: draft create/append/update/delete, send (direct/draft/template), remind, correct recipient email, revise on changes-requested, void, status, audit, downloads (signed + certificate), comments, templates, and account/billing. No obvious dead ends for the domain.