SpriteFuse

Most tools have clearly distinct resource+action targets (jobs vs. assets vs. projects vs. account vs. capabilities), and get_sprite_job versus list_sprite_jobs is unambiguous. The three list_* tools cover different resources but require reading descriptions to separate, and create_sprite_job bundles character/animation/revision creation into one broad entry point, which adds minor ambiguity.

All names follow a snake_case verb_noun convention (create_sprite_job, get_account, list_assets, update_animation_timing), which is highly predictable. The only inconsistency is noun scoping: some tools qualify with 'sprite' or 'animation' while others use bare nouns (account, capabilities, assets, projects).

At 11 tools the surface is well-scoped for an image/sprite generation service, covering job lifecycle, references, exports, account and capability reads, and project/asset listing. Each tool earns its place without redundancy.

Core lifecycle is covered: upload reference, create job, poll job, cancel, list assets/projects, export, and adjust animation timing. Gaps are minor: list_projects has no get/update/delete counterpart, and there's no asset deletion, but normal workflows can proceed.