nex_browser_group_modify

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

With no annotations, the description does add real behavioral constraints: names must stay team-unique and the ungrouped bucket (groupId 0) is rejected. But it does not state what happens on a uniqueness conflict, whether the operation is reversible, or what a successful rename/reorder returns.

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?

Three short sentences, front-loaded with the core action, then constraints. No filler, though the groupId 0 line partially duplicates the schema's groupId description.

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 an unannotated mutation tool with no output schema, the description covers what is changed and the key restrictions but is silent on error behavior, permission requirements, and the result, leaving 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%, so baseline is 3. The description loosely maps rename->name and reorder->seq but adds no format or constraint detail beyond what the schema properties already document.

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?

Specific verb pair (rename/reorder) plus resource (custom window group) and scope (active workspace) let an agent distinguish it from nex_browser_group_create, nex_browser_group_delete, and nex_browser_rename without opening a schema.

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?

Usage context is implied by 'modify one custom window group', and the groupId 0 exclusion is a useful boundary, but the description never names an alternative or says when to choose this over group_create/group_delete. The routing is left to inference.

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