browser_events

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. It discloses an incremental 'since last query' scope and lists included event types, but it does not explain whether calling it advances or clears the cursor, whether it is read-only, or how the 'last query' baseline is maintained.

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 with no wasteful wording. It is efficient, though it lacks a front-loaded verb and is somewhat ambiguous rather than maximally structured.

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 no annotations, no output schema, and no parameters, the description must carry the full context. It enumerates event categories but does not explain the return format, the stateful query behavior, or how the agent should interpret the results.

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 tool has zero parameters, so per the baseline this dimension is naturally strong. There is no parameter behavior to clarify or compensate for in the description.

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 event categories it reports (accepted dialogs, saved downloads, opened popups) and implies a list of events since the last query, but it never uses a clear verb like 'list' or 'return' and does not distinguish itself from siblings such as browser_history or browser_console.

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 this tool versus alternatives, no prerequisites, and no indication of whether it should be called after other browser actions. The agent is left to infer usage from the event categories alone.

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