vibeside_stop_browser

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

No annotations are provided, so the description carries the full burden. It does disclose that the operation terminates a process and deletes temporary user data profiles, which is useful destructive context, but it omits whether cleanup is reversible, what happens if no browser is running (idempotency), and whether any session state is lost.

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 with zero filler, leading with the primary action (terminate) and following with the cleanup side effect. Nothing needs trimming or reordering.

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 two-optional-parameter shutdown tool with no output schema and no annotations, the description covers the essential action and cleanup but leaves gaps around return values, idempotency when nothing is running, and interaction with profile/cluster state. Adequate but not fully complete.

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 both timeoutMs and cleanUserDataDir are already fully documented in the schema with defaults and ranges. The description references the profile-cleanup behavior but adds no syntax, default, or edge-case detail beyond what the schema supplies, matching the baseline 3.

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?

The description gives a specific verb ('Terminate') plus the exact resource ('the spawned Chrome/Edge daemon process'), so the agent knows precisely what the tool acts on. It pairs naturally with vibeside_spawn_browser, though it does not explicitly name that sibling or distinguish itself from vibeside_cluster_shutdown.

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?

Usage is only implied by the spawn/stop pairing with vibeside_spawn_browser; there is no explicit 'use this when shutting down a browser session' or exclusion such as 'does not affect cluster-managed browsers'. No prerequisites or state requirements (e.g., browser must be running) are stated.

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