Start Browser Test

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

Annotations indicate destructiveHint=true and readOnlyHint=false, but the description does not elaborate on what destructive behavior occurs (e.g., terminating previous sessions). It adds context about navigating to a URL but omits details about session lifecycle or async behavior.

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 concise: one sentence for purpose followed by a brief bullet list of parameters. Every sentence adds value, and the structure is clean and front-loaded.

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?

Given the tool's role as a session starter, the description covers core purpose and parameters. Output schema exists, so return values need not be described. However, it could mention that this tool is required before using other browser tools. Overall adequate.

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?

The description adds clear meaning to each parameter beyond the schema titles, including example URL format, default values for headless and viewport, and the purpose of review_mode. Even though schema coverage is 0%, the description compensates well.

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 title 'Start Browser Test' and description 'Start a browser testing session and navigate to the given URL' clearly state the verb (start), resource (browser test session), and specific action (navigate to URL). This distinguishes it from sibling tools like end_session or click_what.

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?

No explicit guidance on when to use this tool versus alternatives (e.g., capsule_restore) or when not to use it. The description implies it is the entry point for browser testing but does not state prerequisites or exclusions.

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