Idle9

Most tools target a distinct resource+action (files, commands, packages, ports, checkpoints, environments) and are easy to tell apart. The one soft spot is the trio list_environments / get_environment_info / get_active_environment, which all return environment metadata and could be momentarily confused, though the descriptions do draw the line between 'which computer is active' and 'status/resources'.

Every tool follows a clean verb_noun snake_case pattern (create_checkpoint, list_environments, expose_port, install_package, run_command). Affixed forms like expose_port/unexpose_port/list_exposed_ports stay predictably related, and there is no mixing of conventions.

18 tools is on the heavier side but each maps to a real operation across six coherent domains (environments, checkpoints, files, commands, packages, ports). Nothing looks redundant, though it sits just above the ideal 3-15 range.

Checkpoints are full CRUD and files/commands/packages/ports are well covered, so core workflows have no dead ends. The notable gap is the absence of delete_environment (and file delete/rename), which matters since create_environment explicitly fails when you're at your machine limit.