nex_browser_group_create

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

With no annotations, the description must convey behavioral traits. It discloses the uniqueness requirement and rejection on duplicate names, which is useful. However, it does not mention success behavior, return value, or any prerequisites like an active browser connection, leaving some ambiguity.

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 that are direct and purposeful: the first states the core action, the second covers a constraint and a follow-up tool. No unnecessary words or repetition.

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 create tool with no output schema and full schema parameter descriptions, the description covers the operation, constraints, and next step. It is missing only minor contextual details such as the return value or whether an active workspace is required, but overall it is sufficient for the task.

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 100%, so the schema already explains both 'name' and 'seq' fully. The description adds no additional parameter meaning beyond reinforcing the uniqueness constraint already in the schema, so it meets the baseline of 3.

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 primary function: 'Create one window group in the active NexBrowser workspace.' It uses a specific verb and resource, and the mention of uniqueness and a follow-up tool distinguishes it from sibling groups like delete and move.

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?

It explicitly guides the next step: 'Use nex_browser_move_to_group afterwards to put windows into the new group.' This provides clear workflow context, though it does not explicitly state when not to use this tool or compare with alternatives beyond the follow-up action.

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