browser_webauthn_bypass

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It reveals that it creates a virtual authenticator via CDP, but fails to mention side effects on browser state, persistence, cleanup, or any setup requirements. This leaves significant behavioral ambiguity.

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 two short sentences with zero filler, front-loaded with the core action and followed by the practical effect. Every word earns its place.

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?

The tool has a well-documented schema and an output schema, so basic invocation details are covered. However, the description lacks usage context, caveats about the 'most' WebAuthn claim, and any relation to sibling tools, leaving open questions about when and how to apply this tool reliably.

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 schema already provides thorough descriptions for both parameters (slot range and rp_id examples/defaults), so the description adds no parameter-specific meaning. Since schema coverage is 100%, the baseline of 3 is appropriate.

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 clearly states that the tool creates a virtual WebAuthn authenticator via CDP, using a specific verb and resource. It also communicates the intended effect ('Bypasses most WebAuthn'), which distinguishes it from sibling tools like browser_inject_passkey.

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 'Bypasses most WebAuthn' implies when the tool might be useful, but there is no explicit guidance on when to use it versus alternatives such as browser_inject_passkey or browser_solve_challenge. No exclusions or prerequisites are mentioned.

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