browser_open_page

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

No annotations are provided, so the description carries the full behavioral burden. It discloses that the page opens in a new controlled window and does not emulate dialogArguments or callbacks, but omits whether it waits for load, returns a window handle, requires permissions, or how the opened window is managed afterward.

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?

Two front-loaded sentences with no filler; the primary action comes first and the limitation follows directly. Every clause adds useful information.

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?

For a one-parameter, no-output-schema, no-annotation tool, the description covers what it does and a key limitation. It still leaves return/interaction details unstated, such as how to target the new window afterward, but core invocation is clear.

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 schema documents only a required string named 'url' with 0% description coverage. The description adds the important constraint that the URL must be absolute and HTTP(S), which meaningfully compensates for the empty schema description, though it provides no examples or further format guidance.

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 ('Open') and resource ('absolute HTTP(S) URL in a new controlled window'), including scope. It does not explicitly name sibling alternatives like browser_navigate, so it stops short of full sibling differentiation.

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?

Gives a concrete usage scenario ('inspected legacy dialog destinations') and an exclusion ('does not emulate dialogArguments or callbacks'), which helps decide when to use it. However, it does not name an alternative tool for normal navigation.

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