Start web debug session

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

Annotations already flag destructive/non-read-only behavior, and the description adds useful behavioral context: one guarded HTTPS loopback origin, a project-contained disposable auth fixture, targetId pinning, and Safari's stricter CSS-only constraint. It does not contradict annotations, though it does not spell out side effects of starting a session.

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?

Three dense sentences front-load the core operation and then layer constraints and optional modes without filler. Every clause adds information about transport, safety, or browser behavior.

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 complex 12-parameter tool, the description conveys the main start/attach paths and key constraints, and an output schema exists so return values need not be described. It still leaves gaps around selecting among transport modes, headless/viewport/allowRemote, and how this tool relates to sibling web debug tools.

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 0%, so the description carries the burden. It gives real meaning to URL, browser choice, CDP/WebDriver/executable transports, tls loopback, authFixture, and targetId. However, headless, viewport, allowRemote, projectRoot, and the precise endpoint/executable fields are left implicit, which is a notable gap for a 12-parameter tool.

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?

Description uses a specific verb ('Start or attach'), names the resource ('local Chromium or Safari page'), and specifies the connection mechanisms (URL plus CDP, WebDriver, or executable settings). This distinguishes it from sibling tools like web_session_status or web_session_close, whose purpose is monitoring or teardown.

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?

It conveys when to use the tool: to begin or attach to an explicitly selected local page for debugging, with browser-specific caveats ('Safari remains strict and CSS-only'). It does not explicitly name sibling alternatives or state when not to use them, so it stops at clear context without exclusions.

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