Each tool maps to a distinct browser action or onboarding step, with clear descriptions separating open/read/click/type/close. guide versus status and open versus read are adjacent but sequencing cues in the descriptions keep them distinguishable.

All tools use a consistent crewnest_ prefix followed by a single lowercase action word in snake_case. The pattern is predictable throughout, even though status is a noun rather than a verb.

Seven tools are well-scoped for a focused browser-automation server tied to one app. The minimal primitive set for onboarding, reading, interacting, and closing a session is covered without bloat.

The core automation loop is complete: guide, status, open, read, click, type, and close cover setup, inspection, interaction, and teardown. Minor gaps such as scrolling, waiting, keyboard submission, or explicit navigation are absent but can often be worked around through read and click.