dialogs

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

No annotations are present, so the description carries the full behavioral burden. 'Return' clearly signals a read operation, and the description adds that each dialog's handling is included. It does not mention whether reading consumes the dialog list, but for a simple parameterless getter this is reasonably transparent.

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 focused sentence that front-loads the verb and resource, then adds specific dialog types and the handling detail. There is no filler or redundancy.

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 and parameterless, but there is no output schema and the description leaves 'how each was handled' underspecified. An agent still lacks a clear sense of the return shape, such as whether handling is expressed as accepted/dismissed, input values, or timestamps.

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 zero properties, so there are no parameter semantics to document. Schema description coverage is 100%, and the description appropriately avoids inventing parameter details where none exist.

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 uses a specific verb ('Return') and identifies a precise resource: JS dialogs of types alert/confirm/prompt/beforeunload. It also states that the result includes handling outcomes, which clearly distinguishes it from siblings like set_dialog_behavior that configure dialog behavior.

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 the tool is for inspecting dialogs that the page has raised, but it does not explicitly state when to use it over alternatives such as set_dialog_behavior or snapshot. No exclusions, prerequisites, or alternative-selection conditions are provided.

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