Scored across 53 tools
Many tools have distinct purposes, but several overlap enough to risk misselection: get_item vs specialized get_password/get_username/get_totp/get_uri/get_notes, list_collections vs list_org_collections, get_collection vs get_org_collection, and send_create vs send_create_encoded. Descriptions help clarify boundaries, but the set is large enough that non-obvious choices remain.
The keychain_ prefix and snake_case are used consistently, making the set predictable. However, ordering is not fully uniform: most tools use keychain_<verb>_<noun>, while the Send family uses keychain_send_<action> (send_get, send_create, send_delete), and a few tools are noun-only names such as keychain_status and keychain_sdk_version.
At 53 tools, this is far above the well-scoped 3-15 range and exceeds the 25+ threshold for being too many. Bitwarden has a broad surface, but many tools are granular CLI wrappers and several have close variants, making the set heavier than necessary.
The surface covers item CRUD for all major item types, folders, organizations, collections, attachments, Sends, search, sync, generation, and exposure checks. The main gap is explicit auth/session lifecycle handling such as unlock/login/logout, which could leave a locked-vault workflow as a dead end.