Browser Read Dialogs

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Read captured...' without explaining whether reading consumes the dialogs, what happens when no dialogs exist, or how the n parameter affects behavior. This is a significant gap for a tool that likely manipulates a queue.

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, front-loaded sentence with no wasted words. It states the core action and target efficiently.

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 presence of three parameters and an output schema, the description is too sparse. It lacks parameter explanations, behavioral details, and usage context. While the tool may be straightforward, the complete absence of parameter or behavioral info makes it inadequate for correct invocation.

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 input schema has 0% description coverage, yet the description does not explain any of the three parameters (n, tab, session). The parameter names are suggestive but not explicit, and the description adds no clarification about their semantics, leaving an agent to guess their meanings.

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 clear verb ('Read') and resource ('captured alert/confirm/prompt dialogs'), making the tool's purpose unambiguous. It is distinct from siblings like browser_dialog_respond (which likely writes) and browser_set_dialog_mode (which configures handling), though it does not explicitly differentiate itself.

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 provides no guidance on when to use this tool versus alternatives such as browser_dialog_respond or browser_set_dialog_mode. It is implied that reading is appropriate when dialogs have been captured, but no explicit conditions or exclusions are given.

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