List tab groups

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

readOnlyHint=true already declares the safety profile, so the description only needs to add context — and it does, by disclosing exactly what is enumerated (id, label, colour, collapsed state, contained tabs). It adds no cost, rate-limit, or ordering caveats, but for a local read-only enumerator there is little to disclose.

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 front-loaded sentences with the return shape first and the follow-up routing second — no waste. The parenthetical internal API name (gBrowser.getAllTabGroups) is trivia an agent cannot act on and is the only removable content.

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?

With no output schema, the description carries the return-value burden and does so by naming every field plus the nested tabs. Combined with annotations covering read-only safety and a parameterless schema, nothing needed 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?

The tool takes zero parameters, so there is nothing for the description to disambiguate; the baseline of 4 applies. The description correctly implies an unscoped 'list all groups' call rather than suggesting any filter exists.

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 (List) and resource (tab groups), then defines the resource in-domain ('collapsible groups in the tab strip') and enumerates the returned fields. An agent can distinguish this from browser_list_tabs without opening the 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?

Gives concrete downstream usage: 'Use the id with browser_remove_tab_group or browser_ungroup_tabs', which tells the agent why to call this first. It does not explicitly exclude browser_list_tabs or state that this is the only source of group ids, so it falls short of full when/when-not routing.

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