The five browser primitives (open, read, click, type, close) have clearly distinct roles, and setmore_guide vs setmore_status are mostly separable (how-to vs readiness check). The only mild overlap is between guide and status, both of which are introductory 'call me first' helpers, but descriptions give enough cues to pick correctly.

All tools share a consistent setmore_ prefix and snake_case form. The action words are verbs for the browser primitives, but guide and status are noun-style names, a minor deviation from a pure verb_noun pattern.

Seven tools is well-scoped for a browser-automation wrapper over a single SaaS app. Each tool corresponds to a necessary step in the open-read-act-close loop, with no padding.

The core loop is covered, but common browser interactions are missing: no key press/submit (e.g. Enter), no select/dropdown option tool, and no explicit scroll or wait. Agents can often work around these via click targets, but they risk dead ends on forms or long pages.