browser_tabs

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, which the description aligns with. The description adds minimal behavioral detail beyond the schema, such as 'if omitted for close, current tab is closed,' but does not elaborate on consequences of create or select.

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?

The description is a single, clear sentence covering all intended actions. It is efficient but lacks structural elements like bullet points or separate lines for each action, though not necessary given brevity.

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 tab management tool with multiple actions and no output schema, the description covers the core functionality but omits details like what happens when listing empty tabs, the effect of 'select' on focus, or error states. It is minimally adequate.

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?

Input schema has 100% coverage with descriptions for action, index, and url. The description only restates the actions and does not add new semantics or examples for parameter usage.

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 explicitly states the four actions (list, create, close, select) and the resource (browser tab). It clearly distinguishes from sibling tools like browser_navigate (which operates within a tab) and browser_close (which likely closes the browser, not a tab).

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 for basic tab management but provides no explicit guidance on when to use this tool versus alternatives like browser_navigate or browser_close. It does not mention prerequisites or when not to use it.

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