browser_tabs

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered upstream. The description adds nothing beyond repeating the action list: it does not say that 'close' discards tab state, that 'list' is a harmless read within an otherwise destructive tool, or that the four modes have very different risk profiles.

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?

A single front-loaded sentence with zero filler; the verb enumeration comes first. It is efficient, though the terseness is part of why usage context is thin rather than a fault of structure.

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?

This is a multi-mode tool bundling a safe read ('list') with destructive operations ('close'), with no output schema and no annotations explaining per-mode differences. Given the crowded sibling set (browser_navigate, browser_close, session_create), the one-line description leaves the agent without enough context to route between tools confidently.

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 description coverage is 100%, and every parameter (url, index, action, session) has a documented meaning including conditional use ('used for close/select', default session semantics). The description adds no parameter meaning beyond the schema, so the 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?

The description names the resource (browser tab) and enumerates the four supported verbs (list, create, close, select), so the agent knows exactly what capability it exposes. It does not differentiate from close siblings such as browser_navigate or browser_close, which a reader might reasonably confuse with 'new' and 'close' here.

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?

There is no guidance on when to pick this tool over browser_navigate for opening a URL or browser_close for shutting down, nor any stated preconditions such as requiring an existing page. The agent is left to infer that 'new' supersedes navigation behavior.

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