kontato

Most tools target distinct resources/actions (send vs call vs schedule vs provision). The main overlap is send vs reply (reply is essentially send with a required 'to'), and status partially overlaps with list_schedules/list_recipients, but descriptions clearly explain the boundaries.

There is a consistent verb_noun pattern for lifecycle operations (authorize_recipient, cancel_schedule, get_call, list_messages, list_recipients, list_schedules, verify_number). The primary actions use bare verbs (send, reply, call, schedule, provision) and one noun (status), which is a minor stylistic deviation but still readable and predictable.

13 tools is well within the ideal 3-15 range and each covers a distinct capability: provisioning/verification, messaging, voice calls, scheduling, and listing. Nothing feels redundant or padded for the scope of a WhatsApp bridge.

The surface covers the full lifecycle: provision/verify, send/reply, call/get_call, schedule/cancel/list, plus authorization of recipients. A minor gap is the absence of a revoke/de-authorize recipient or an update-schedule operation, but core workflows are complete.