browser_overlay

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

No annotations are provided, so the description carries the full burden. It discloses that dismiss mode automatically clicks to close overlays (implying mutation), and detect mode identifies elements. However, it does not detail side effects (e.g., page changes), permission needs, or whether the operation is reversible. Given the tool's simplicity, this is adequate but not thorough.

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 two sentences long, directly stating the purpose and sub-modes. It is front-loaded with the main functionality and avoids unnecessary details, making it efficient for an agent to parse.

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 has no output schema, so the description should explain what the tool returns (e.g., detected overlays, success status). The description only mentions actions ('detect' and 'dismiss') but does not describe the output format or expected results, leaving a gap for the agent to infer the return value.

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 coverage is 100% with descriptive enum values. The description adds context about the merger version but does not significantly enhance understanding beyond the schema. The parameter descriptions in the schema already cover the meaning of 'mode' and 'format'.

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's purpose: detecting and dismissing overlays like popups and banners. It explicitly mentions that it is a merged tool (v1.9.5) combining two previous tools, which distinguishes it from siblings like browser_overlay_detect and browser_overlay_dismiss.

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 the two modes (detect and dismiss) with defaults, implying when each mode should be used. However, it does not provide explicit guidance on when to use this tool versus alternative approaches (e.g., browser_click for manual closing), nor does it state prerequisites or when not to use it.

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