create_window

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

No annotations are provided, so the description carries the behavioral burden. It discloses that this is a create operation, that profile_id is required and must come from profiles_list, and that object IDs are profile-local. It does not cover permission requirements, failure modes, or side effects beyond the obvious creation of a browser window.

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, front-loaded with the core action. The second sentence is dense but every clause adds useful constraint information: required profile_id, source, and profile-local ID scoping.

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?

With 10 parameters, one required, an output schema, and 90% schema description coverage, the structured data carries most detail. The description supplies the key missing operational context: the required profile_id, where to get it, and the profile-local ID constraint. Minor gaps remain around when to choose this over tab-creation or other window tools.

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 already 90%, so most parameters are documented structurally. The description adds meaningful semantics for the required profile_id by specifying where to obtain it and warning that object IDs are local to that profile and must not be reused elsewhere.

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 states a specific verb and resource: 'Create a new browser window.' This clearly separates it from window-management siblings like list_windows, get_window, close_window, and update_window, and from tab creation. It does not explicitly name an alternative, but the resource distinction is strong enough for correct tool selection.

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 provides a prerequisite for profile_id and says to obtain it from profiles_list, which is useful guidance. However, it does not explain when to create a window versus creating a tab or using another window tool, nor does it state exclusions or alternatives.

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