Act In Browser

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

No annotations are provided, so the description bears full responsibility. It only says 'run one native mouse or keyboard action' without disclosing side effects, token lifecycle, reversibility, or required permissions. This is insufficient for a tool performing potentially destructive actions.

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 sentence, highly concise and front-loaded with the core purpose. However, it omits important details that would improve usability, slightly reducing its effectiveness.

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?

Given the complexity of the action parameter (13 variants) and no output schema, the description is severely lacking. It does not explain how to construct actions, the meaning of 'fresh' token, or what the tool returns, making it incomplete for practical use.

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?

The schema description coverage is 0%, and the description adds no explanation of the observationToken or action parameters. It does not elaborate on the complex action structure, leaving agents to infer meaning solely from the schema, which is inadequate for effective selection and invocation.

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 clearly states 'Run one native mouse or keyboard action against a matching fresh browser_observe token,' which specifies the verb (run), resource (action against browser), and distinguishes from sibling tools like browser_observe (observation) and browser_stop (stop).

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 implies usage context by mentioning 'matching fresh browser_observe token,' indicating dependence on the browser_observe tool. However, it does not explicitly state when to use this tool versus alternatives or when not to use it, leaving room for ambiguity.

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