Act on the page

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is covered. The description adds meaningful behavior beyond annotations by disclosing that intent mode spends model quota and that --jev-decider controls whether Jev or the text model answers. It still does not describe side effects or what the operation returns, but it adds useful operational context.

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 front-loads the operation list before explaining target and intent modes. Every sentence contributes, though the final sentence is somewhat cryptic with 'Both' and '--jev-decider' requiring outside context.

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 five-parameter action tool with no output schema, the definition explains operation modes and target handling adequately. It does not explain how an observation is obtained, what the tool returns after acting, or how errors are surfaced, which leaves meaningful gaps for an agent planning a browser interaction sequence.

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 100%, and the schema already documents text, intent, target, operation, and observation individually. The description mostly restates those semantics, reinforcing that CLICK/TYPE_TEXT/SELECT take a target and SCROLL/WAIT do not, but it adds little beyond the schema itself. Baseline 3 is appropriate.

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 states a specific verb and resource: run one operation on one target from an observation, with an explicit list of supported operations. It is clear what the tool does, but it does not differentiate itself from siblings such as browser_eval or browser_goal, leaving the agent to infer the boundary.

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?

It clearly explains the two modes: explicit operation plus target, or omit both and provide an intent for the policy to choose. It also specifies which operations need a target and that TYPE_TEXT may take text. However, it gives no guidance on when to use this tool instead of sibling tools like browser_eval or browser_page.

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