browser_act

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

No annotations exist, so the description carries the burden. It discloses selector compatibility and provides an example, but it omits behavioral details such as side effects, failure modes, or authentication requirements. The visible constraints are useful but not comprehensive.

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 compact and well-structured into Purpose, Constraints, and Example. Every sentence contributes value, though the trailing ellipsis after the action list is slightly untidy.

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?

The description covers the core purpose, action-target compatibility, and gives an example, but with 7 parameters and no in-schema descriptions, it leaves gaps around exact/name semantics and return behavior. The output schema exists but is not included, so the description alone is not fully complete.

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 parameter descriptions are entirely absent (0% coverage), so the description must compensate. It explains the interplay between action and target_type, references name/exact for accessible matching, and supplies a concrete example with action, target, value, and session.

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 opens with a specific verb and resource: 'Interact with a page element' and enumerates all supported actions (click, fill, type, press, hover, select, check/uncheck). This clearly differentiates it from sibling browser tools like browser_open or browser_snapshot.

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?

Provides explicit guidance on when to use snapshot refs and which target types support which actions. It does not explicitly contrast with alternatives like browser_eval, but the constraints are clear enough to guide selection.

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