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

Annotations already indicate non-read-only and non-idempotent behavior, but the description adds that the tool blocks/wait for the owner and references the live view mechanism. The security warning about passwords is a behavioral boundary not captured in annotations. This goes beyond the structured data and clarifies how the tool affects the flow.

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?

Two sentences with zero redundancy. The core function is front-loaded, and the warning is placed second. Every phrase earns its place, and the structure is immediately scannable.

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 description, combined with the enum and annotations, covers the essential aspects for calling the tool correctly. It lacks details about what happens after the pause (e.g., how the user signals completion), but the output schema exists and the tool's simplicity reduces the need for more. The warning about passwords is an important addition.

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 coverage is 100%, so both parameters and the enum values are fully described in the schema. The description only repeats the enum values ('login, CAPTCHA, 2FA, or review') without adding extra meaning. With high schema coverage, the baseline 3 suffices; no additional clarification is needed.

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 ('Pause for') and the resource ('Owner login, CAPTCHA, 2FA, or review') with a clear location ('Browserbase live view'). It also adds a crucial negative instruction ('Never ask the Owner to paste passwords into chat'), which distinguishes it from other owner-interaction tools. This clearly differentiates from siblings like confirm_and_submit or wait_for_user_ready.

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 description lists exact scenarios (login, CAPTCHA, 2FA, review) that trigger the pause, making the 'when' explicit. However, it does not contrast with alternative tools (e.g., wait_for_user_ready) or state when not to use it. Despite that, the enum in the schema reinforces these use cases, so the guidance is strong.

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