List browser popup notifications

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

readOnlyHint=true is consistent with a "List" verb and is not contradicted. The description adds useful domain context (these are browser-native prompts, not page dialogs) but says nothing about the returned items — whether they carry identifiers, expire, or are per-tab — which is exactly what an agent needs before handing off to the accept tool.

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?

Three short sentences, front-loaded with the verb+resource, then gloss, then follow-up action. The parenthetical examples earn their place; nothing is redundant.

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?

There is no output schema, so the description should hint at the shape of the result — an agent cannot tell how to reference a specific notification when calling browser_accept_popup_notification. Annotation and parameter coverage are otherwise sufficient for a no-arg read tool.

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?

Zero parameters and 100% schema coverage, so there is nothing for the description to compensate for. Baseline 4 applies.

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?

States a specific verb and resource (list browser doorhanger notifications) and disambiguates with a concrete gloss — the "Save password?" / "Remember this site" prompts Firefox shows after a form submit. The one gap is that it never distinguishes itself from the sibling browser_list_prompts / browser_handle_prompt, which an agent could plausibly confuse with this.

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?

Explicitly pairs the tool with its action counterpart ("use browser_accept_popup_notification to press one") and frames the real-world goal (programmatic "remember the password"). It gives no exclusions, though — nothing says when to prefer browser_list_prompts or what to do if the list is empty.

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