nex_browser_group_delete

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

Beyond the destructiveHint annotation, the description adds important context: windows inside the group are not deleted but ungrouped, and the ungrouped bucket (groupId 0) cannot be deleted. This clarifies side effects and a limitation, though it doesn't cover all potential failure modes like invalid group IDs.

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 sentences, front-loaded with the action, and no filler. The first sentence states what it deletes and where, the second clarifies side effects and a restriction, earning every word.

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?

Given one parameter, no output schema, and a destructive annotation, the description covers the essential context: deletion scope, ungrouping behavior, and the 0 restriction. It omits details about return values and non-existent group handling, but the core usage is sufficiently complete.

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 schema already fully describes the groupId parameter with 100% coverage, including the rejection of 0. The description reiterates this but adds no new semantic information beyond what the schema provides, so the baseline of 3 is appropriate.

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 'Delete one custom window group from the active NexBrowser workspace' with a specific verb and resource. It distinguishes from sibling tools like group_create, group_list, and move_to_group by focusing on deletion, and adds scope (active workspace).

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 implies usage by explaining the effect (windows become ungrouped) and the groupId 0 restriction, but it doesn't explicitly say when to use this tool versus alternatives such as move_to_group. No explicit 'when-not' or alternative recommendations are given.

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