browser_wait_for

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

With no annotations supplied, the description carries full behavioral burden. It does disclose the wait semantics and that network idle means pending API/fetch requests finish, but it never states what happens on timeout (throw, return false, silent success), whether the call blocks the agent, or whether selecting among ref/selector/text changes 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?

A single front-loaded sentence with no filler; the condition list is packed efficiently into one clause. It is slightly awkward syntactically ('or waits for network idle' breaks the parallel structure of the state list), but nothing is wasted.

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?

Six optional parameters, no annotations, and no output schema mean the description is the only place to explain failure behavior and how the mutually exclusive element locators (ref vs selector vs text) interact. It explains the conditions but not the outcome of a failed wait, which is the main thing an agent needs to handle.

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 100%, so the schema already documents ref, text, state, tabId, timeout, and selector, making 3 the baseline. The description's only added meaning, the parenthetical about pending API/fetch requests, is already present in the schema's own enum description, so nothing new is contributed.

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?

Names a specific verb (waits for) and a specific resource (an element) plus the network-idle mode, which clearly distinguishes it from action siblings like browser_click or browser_get_dom. The one gap: 'appear' is not one of the enumerated states in the schema, so the purpose is slightly looser than the schema allows, and no sibling is named for contrast.

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?

There is no explicit when-to-use or when-not-to-use guidance, no mention of what to do instead of this tool (e.g., polling, browser_evaluate), and no statement of prerequisites such as a tab/context existing or a prior browser_navigate. Usage is only weakly implied by the list of states.

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