act

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

No annotations are provided, so the description carries the full behavioral burden, and it discloses nothing: no mention of destructive effects, focus requirements, wait/retry behavior, auth needs, or what happens on failure. For a 17-parameter interaction tool spanning drag, upload, and form submission, this is a serious omission.

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 single line is short, but nearly all of its content duplicates the action enum already present in the schema, and the trailing ellipsis signals an unfinished thought. It is under-specified rather than efficient, so size is not the problem—value per word is.

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?

With 17 parameters, 12% schema coverage, no annotations, and no output schema, the description is the only place an agent could learn behavioral expectations—and it provides none. Nothing about per-action parameter requirements, side effects, or result handling is covered, leaving the definition wholly inadequate for the tool's complexity.

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 12% across 17 parameters, so the description must compensate, and it does not. It restates the action enum but says nothing about how x/y pair with coordinates, how ref/selector/fromRef/toRef relate, or which params are required per action (e.g., type needs text/value, upload needs filePath).

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 names the tool's domain by enumerating the actions it supports (click, hover, drag, type, form, upload, scroll), which hints at browser/page interaction. However, 'DO something' is an empty verb and it never states the resource being acted on, nor does it distinguish act from siblings like browse or find. Purpose is inferable from the enum list, not from a clear statement.

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 guidance on when to use act versus browse, find, page_slice, or tabs, and no exclusions or prerequisites. An agent must infer that this is the interaction tool purely from the action names. No when-to-use context is supplied at all.

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