nex_browser_wait_for

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

With no annotations, the description carries the full burden of behavioral disclosure. It does not specify what happens on timeout (error vs. return), how multiple conditions (target, text, time) are combined, or whether the operation is read-only. This is a significant gap.

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, front-loaded sentence with no fluff. It is concise and easy to parse, though slightly under-specified. It earns its place but could include more detail without losing conciseness.

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 six optional parameters, no output schema, and no annotations, the description is incomplete. It does not explain return values, failure behavior, condition precedence, or the relationship between 'time' and 'timeout'. An agent would have to infer important behavioral details.

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 only 50%, and the tool description does not compensate. It mentions 'target, text, or bounded duration' but does not disambiguate the 'time' vs 'timeout' parameters or explain the semantics of 'text' and 'target' in practical terms. The meaning of these parameters remains ambiguous.

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 uses a specific verb ('Wait') and names target, text, and bounded duration, clearly distinguishing it from sibling browser actions like click or navigate. It lacks a bit of specificity about what 'target' and 'text' refer to, but the core purpose is understandable.

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?

No guidance is provided on when to use this tool versus alternatives. It does not mention suitable scenarios (e.g., after navigation or before clicking) or exclude cases where other tools (such as explicit waits in code) are preferable.

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