vibeside_switch_profile

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations exist, so the description carries the full behavioral burden, yet it says nothing about side effects: whether switching destroys the current session, whether it requires a running browser, or what the passphrase/snapshot interaction implies. The one genuinely behavioral detail (browser-restart re-spawns the daemon) lives in the schema, not the description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

A single well-formed sentence that front-loads the core action and tucks the optional strategies into a trailing clause. No wasted words, though it is arguably too terse given the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a stateful mutation with five parameters, no annotations, and no output schema, the description omits what happens to the current session, whether the operation is reversible, and what a successful switch returns. The schema covers parameters well, but the behavioral surface is largely unexplained.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already fully explains name, navigate, passphrase, switchMode, and snapshotName, including the enum semantics. The description adds no parameter-level meaning beyond what the schema provides, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb (switch) and resource (active browser profile) and names the two switch strategies, clearly separating it from create/list/delete_profile siblings. It does not, however, differentiate itself from vibeside_restore_session_snapshot, which overlaps heavily with the hot-restore path.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies when each mode applies (restart vs hot session restore), but gives no explicit when-to-use guidance versus restore_session_snapshot or spawn_browser, and no prerequisites or exclusions. Usage is left to inference from the mode names.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.