Flask

Most tools map to clearly distinct resources and actions, and the descriptions explicitly disambiguate adjacent operations such as feedback_list vs recent_activity and get_annotated_frames vs get_frame. However, with 29 tools there are several neighboring feedback, upload, and version operations that still require careful reading, so a few boundaries could be confused.

All names use snake_case, but the convention is mixed: resource_action (feedback_post, folder_create), action_resource (get_frame, upload_video), and bare nouns (contents, tags, search) all appear. This remains readable, but there is no single predictable naming pattern across the set.

At 29 tools, the surface exceeds the typical 3-15 range and the 25+ heavy threshold. The domain is complex enough to justify many tools, but specialized operations like get_guide, versions_reorder, versions_split, and separate upload_start/complete calls make the set heavy for routine agent selection.

The set covers the core review workflow well: browsing, search, uploads, processing status, versions, notes and files, feedback CRUD, annotations, tags, permissions, and sharing. The main gap is the absence of deletion operations for assets, folders, feedback, and tags, but deletion is not central to the described review workflow.