browser_create_window

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 says nothing about whether the new window becomes focused/active, how the incognito flag changes behavior or isolation, or whether the created window persists across other tool calls — all material for a window-creation 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?

Two short sentences, front-loaded with the core action and with zero filler. It is efficient, though the terseness is partly the source of the missing detail penalized in other dimensions.

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 creation tool with no annotations, no output schema, and siblings such as browser_close_window, browser_focus_window, and browser_windows that presumably operate on a window identifier, the description never indicates what the call returns or how the new window is referenced later. That gap leaves the agent unable to chain calls correctly.

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 description coverage is 0% for both parameters. The description explains 'url' adequately ('pass a URL to load it at start'), but says nothing at all about the 'incognito' boolean, which is exactly the kind of flag an agent needs explained. Half the parameters remain undocumented in both schema and description.

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: 'Open a new browser window,' which is clearly distinct from the tab-oriented siblings in name. However, it never explicitly contrasts itself with browser_new_tab or browser_navigate, so the agent must infer the window-vs-tab distinction from the name alone.

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 only guidance is 'Pass a URL to load it at start,' which is parameter advice rather than usage guidance. There is no indication of when to create a new window versus a new tab (browser_new_tab), when to navigate an existing window (browser_navigate), or any prerequisite/ordering constraint.

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