browser_wait_for_title

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

No annotations are provided, so the description carries the full behavioral burden. It states the waiting condition but omits critical wait behavior such as what happens on timeout, whether it blocks, and how the regex is applied to the title.

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?

A single, front-loaded sentence with no wasted words. It earns its place by naming the exact condition being waited on.

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?

There are no annotations, no output schema, and incomplete parameter coverage. For a wait tool with tab targeting and a configurable timeout, the description should disclose timeout behavior and tab_id semantics but does not.

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% across three parameters. The description explains that 'pattern' is a JS regex for document.title, but it says nothing about tab_id or timeout, so two of three parameters remain semantically undocumented.

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?

States a specific verb ('Wait until'), resource ('document.title'), and condition ('matches a JS regex pattern'). This clearly distinguishes it from sibling wait tools such as browser_wait_for_url and browser_wait_for_element.

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 gives no guidance on when to use this tool versus browser_wait_for_url, browser_wait_for_element, or browser_wait_for_result. It also does not state any preconditions or when not to use it.

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