browser_tab_group

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

No annotations provided, so description carries full burden. It describes actions and parameter effects (e.g., delete optionally closes tabs, default true). However, it does not explain error handling, success responses, or potential side effects beyond the described actions.

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?

Very concise, with bullet-pointed actions and a clear, front-loaded important note. No extraneous text; every sentence serves a purpose.

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 the tool's moderate complexity (5 parameters, no output schema), the description fully covers the workflow (create before use), all actions, and key parameter roles. It references sibling tools and provides actionable guidance.

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 adds context for some parameters (e.g., groupId for delete, name/color for create) but does not significantly enhance the meaning beyond the schema's own descriptions.

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 that the tool manages tab groups for session isolation and lists three specific actions (create, list, delete). It distinguishes from sibling tools like browser_tabs by explaining that tab groups must be created first and the groupId passed to other tools.

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 states when to create a tab group: 'Multiple users/agents sharing one browser MUST create a tab group first', and provides an important note: 'Always create a tab group before opening tabs with browser_tabs.' This guides the agent on proper ordering.

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