browser_wait

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

No annotations are provided, so the description carries the full burden. It states the tool waits, implying blocking behavior, but does not disclose timeout handling, return values, or what happens when the condition is never met. This is a minimal behavioral disclosure that leaves critical aspects ambiguous.

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 a single short phrase with no wasted words, which is concise. However, it is under-specified and lacks structure; it does not prioritize key information or provide any supporting details. Being short is not necessarily good if it sacrifices necessary content.

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?

For a tool with 5 optional parameters and no output schema, the description is incomplete. It omits what happens when no condition is supplied, how timeouts work, and what the tool returns upon success or failure. The presence of many sibling tools suggests the agent needs more context to avoid misusing it.

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 provides 100% coverage with descriptions for each parameter (url, text, session, timeout, selector). The tool description loosely maps to these (element/text/URL), but does not explain whether parameters are mutually exclusive, combinable, or how they interact. It adds marginal value over the schema without clarifying usage semantics.

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 the tool waits for an element, text, or URL pattern, specifying both the action and the resource types. However, it does not differentiate from siblings like browser_find (which might also locate elements) or browser_state (which could check conditions), missing an opportunity to distinguish itself.

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 alternatives. It does not mention any sibling tools, conditions for use, or exclusions. An agent would have to infer that browser_wait is for synchronous waiting, but nothing explicitly helps with tool selection.

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