Browser Set Dialog Mode

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

With no annotations, the description carries the full behavioral burden. It discloses that auto accepts and records dialogs, and manual pauses them for response. It doesn't mention side effects like whether switching modes clears queued dialogs or if the setting persists across sessions, but the core behavior is clearly stated for a simple setter.

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, concise sentence that front-loads the purpose and explains both modes with zero wasted words. It is perfectly structured for quick comprehension.

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?

The tool is simple, but the description omits any explanation of the 'tab' and 'session' parameters, which are present in the schema. It also doesn't clarify whether the mode applies globally or per-tab. Given the lack of annotations and 0% schema coverage, the description should compensate for these gaps, but it only covers the mode parameter. This is a notable gap for a complete definition.

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 description adds meaning to the 'mode' parameter by explaining the two valid values and their effects, which the schema lacks (0% schema coverage). However, it does not address 'tab' or 'session' parameters at all, leaving them unexplained. Since mode is the primary parameter and tab/session have defaults, this is partial but not complete compensation.

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 action (Set dialog handling) and precisely defines the two modes with their effects ('auto' accepts and records, 'manual' pauses for browser_dialog_respond). This clearly differentiates it from siblings like browser_dialog_respond and browser_read_dialogs, which handle or read dialogs.

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 explains that manual mode pauses dialogs so browser_dialog_respond can answer them, giving a clear use case for when to choose manual. However, it doesn't explicitly contrast with auto mode beyond noting it's the default, nor does it discuss other alternatives or when to avoid this tool. The implication is present but not fully explicit.

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