browser_watch

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

No annotations are provided, so the description is the sole source of behavioral information. It explains the lifecycle (start, poll, stop) but does not disclose potential performance impact, resource usage, or what happens to stored events after polling. The schema clarifies that 'poll' gets events 'since last poll', hinting at destructiveness, but the description omits this detail.

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?

Two concise sentences that efficiently communicate the tool's purpose and usage pattern. The 'GROUNDBREAKING' hype adds no informational value but does not detract from conciseness.

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?

No output schema is provided, and the description does not specify the format or structure of poll results, which is critical for an event-capturing tool. The workflow is clear, but the lack of return value details leaves the agent guessing about how to interpret 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?

Schema description coverage is 100%, so the description adds limited value. It mentions event types like 'exceptions' which are not in the enum (schema lists 'console', 'network', 'navigation', 'all'), creating a minor inconsistency. Otherwise, the description reiterates the action parameter's phases.

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 the tool captures live page events (console, network, navigation, exceptions). It distinguishes itself from sibling tools like browser_screenshot or browser_click, which do not offer event capture.

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 a workflow (start, browse, poll) but does not explicitly state when to use this tool over alternatives or when not to use it. The phrase 'First tool of its kind' suggests uniqueness but lacks direct guidance.

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