Every tool targets a distinct resource plus action: get_* queries are cleanly separated by target (version, login, status, friend_list, group_list, group_info, member_list, member_info, msg, forward_msg, image, record, cookies, csrf_token), and set_* management actions each modify a clearly different attribute. There is no meaningful overlap between any two tools.

The get_/set_ verb_noun pattern dominates and is applied consistently across the large majority of tools, and what reads as 'set' vs 'kick/admin/ban' maps to the underlying OneBot action names. Minor deviations like send_like and delete_msg break the prefix scheme but remain readable and memorable.

27 tools is on the heavy side, but they map one-to-one onto distinct OneBot11 API actions (queries, media, credentials, group administration, requests), so each largely earns its place. It is slightly over the ideal range but not bloated with redundancy.

The set covers querying, media retrieval, credentials, and extensive group administration, but the most essential chat operation — sending a message (send_msg / send_group_msg / send_private_msg) — is entirely absent, along with message history and friend-request listing. For a messaging bot this is a notable and surprising gap.