Write Brave CDP flags and optionally restart Brave so Playwright can attach. Set restart=true when CDP is down.
Write Brave CDP flags and optionally restart Brave so Playwright can attach. Restarts the user's Brave (tabs usually restore). Use restart=true when CDP is down.
| Name | Required | Description | Default |
|---|---|---|---|
| restart | No | If true, restart Brave even if CDP is already up. If omitted, restart only when CDP is down. |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It usefully discloses the key side effect ('Restarts the user's Brave') and a mitigation ('tabs usually restore'), which are important behavioral traits. It still omits details like whether flags are persistent, whether unsaved data may be lost, or whether repeated calls are safe.
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?
The description is three short sentences with no wasted wording. Purpose is front-loaded, followed by a behavioral warning and then a parameter usage note, making it easy to parse quickly.
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 simple one-parameter setup tool with no output schema, the description covers purpose, primary side effect, and parameter usage adequately. It lacks explicit guidance on when to choose this tool over browser_status or other preparatory alternatives, but otherwise gives enough context to call it correctly.
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% and the single restart parameter is fully documented in the schema. The description's 'Use restart=true when CDP is down' largely repeats the schema's own explanation, adding no meaningful semantic detail beyond what structured data already provides.
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 states a specific verb and resource: 'Write Brave CDP flags' and 'restart Brave so Playwright can attach.' It clearly identifies a setup/preparation tool, distinguishing it implicitly from the browser_* action siblings, though it does not explicitly name or compare against any sibling.
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 phrase 'so Playwright can attach' gives implied context for when to call the tool, and 'Use restart=true when CDP is down' provides a condition for the parameter. However, there is no explicit guidance on when to use this tool versus browser_status or other siblings, and no when-not guidance.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.