chrome_windows

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

No annotations are provided, so the description carries the full burden of explaining behavior. It discloses that listing shows all windows and their tabs, but it does not describe side effects, permissions, focus behavior, or the response format. The unsupported 'focus a specific window' claim further muddies what the tool actually does.

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 short and front-loaded, with the core list behavior stated early. The generic word 'Manage' and the false focus capability are minor structural flaws, but overall the description is not bloated.

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 simple one-action tool, the description is mostly adequate: it says the action lists windows and their tabs. But the false focus claim, lack of output details, and absence of guidance about when to prefer this tool over sibling window/tab tools leave meaningful gaps.

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 coverage is 100% and the sole parameter (action) has a clear enum description in the schema. The tool description adds little parameter-level meaning and even implies a focus action that does not exist in the enum, so it does not improve on the schema.

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 identifies the resource (Chrome windows) and the main operation (list windows with tabs), which is helpful. However, it also states the tool can 'focus a specific window,' while the schema only allows action='list', making the stated purpose partially inaccurate.

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?

There is no explicit guidance on when to use this tool versus siblings like browser_tabs, chrome_focus, or browser_snapshot. The phrase 'each window groups multiple tabs' implies a window-level view, but no direct comparison, exclusions, or recommended conditions are provided.

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