List active workspace window groups with window counts to select a groupId for creating, moving, or deleting windows.
List the window groups of the active NexBrowser workspace with the window count of each, so a groupId can be selected for window creation, moving, or deletion. The first row is always the ungrouped bucket with groupId 0.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v2026.8.14Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The readOnlyHint annotation already signals non-destructiveness, and the description adds valuable behavioral context—specifically that the first row is always the ungrouped bucket with groupId 0. This goes beyond the annotation by explaining what to expect in the list output.
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, with the action and purpose front-loaded in the first sentence. The second sentence adds a critical detail (groupId 0) without any fluff. Every word is purposeful.
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 read-only list tool with no parameters and no output schema, the description covers the core functionality: listing window groups with their counts in the active workspace, and the special ungrouped bucket. It could optionally detail the exact output format, but the phrase 'with the window count of each' conveys the essential return value.
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 tool takes zero parameters, and the schema is trivially complete. The description does not need to explain parameters, and the context signals confirm 100% schema coverage. This meets the baseline for a zero-parameter tool.
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 clearly states the verb 'List', the target resource 'window groups of the active NexBrowser workspace', and the output detail 'with the window count of each'. It distinguishes this from sibling tools like tab_list or group_delete by specifically focusing on window groups and groupId 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 explicitly states the intended use: to select a groupId for window creation, moving, or deletion. It also highlights the special ungrouped bucket with groupId 0, which is important for using group-related tools. However, it does not explicitly mention alternative tools or when not to use this tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.