Remove a tab group

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

With only readOnlyHint=false in annotations, the description carries the critical disclosure: the default path closes the tabs, while ungroup:true preserves them. That is exactly the destructive-vs-safe distinction an agent must know before invoking it.

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, zero filler, with the destructive default surfaced before the id-sourcing pointer. Nothing could be removed without losing meaning.

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 two-parameter, one-required tool with no output schema and full schema coverage, the description covers purpose, safety semantics, and id source. Nothing an agent needs to call it correctly is missing.

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 both parameters are already documented in the schema, including the 'default false = close tabs' note. The description restates that semantics rather than adding new detail, so baseline 3 applies.

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?

States a specific verb and resource ('Remove a tab group by id') and even names the underlying platform call. It is clearly distinguishable from siblings like browser_group_tabs, browser_move_tab_to_group, and browser_list_tab_groups.

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?

Explicitly routes the agent to browser_list_tab_groups for obtaining ids, which is the key prerequisite. It also frames the ungroup decision as a conditional, though it does not name a non-destructive alternative tool (e.g. tab closing) as a contrast case.

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