Perform bounded browser action

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

Annotations already carry safety and side-effect hints (destructive=true, readOnly=false). The description adds useful context about the bounded same-origin scope, exact locators, and live probe waits. However, it does not disclose side effects or failure modes beyond what the annotations imply, so it earns a middle score rather than lower.

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 dense sentence enumerates the full action set without wasted words. The core action list is front-loaded, though the phrasing 'fresh live probe waits' is slightly opaque and could have been clearer.

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?

This is a highly complex tool with ten action variants, five locator types, and a wait mechanism, yet the description only lists actions and mentions same-origin scope. It omits guidance on how action kinds interact with locators, when waits are needed, timeout defaults, or what outputs are produced. An output schema exists, but the description still under-specifies for an agent deciding correct invocation.

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%, so the description must compensate. While it lists the action kinds, it adds no meaning about the sessionId parameter, locator variants, value semantics, wait properties, or timeout behavior. The schema is self-explanatory for structure, but the description contributes almost nothing to parameter understanding.

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 enumerates a specific list of actions (navigate, click, fill, press, etc.) and names the resource scope ('selected same-origin target'), making the tool's function clear. It doesn't explicitly distinguish itself from sibling tools, but the action list and bounded-scope phrasing set it apart from session lifecycle and inspection siblings.

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 about when to use this tool versus the sibling tools such as web_next_inspect, web_issue_capture, or web_session_start. It does not state any exclusions, prerequisites, or alternative conditions.

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