browser_tabs

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

With no annotations, the description carries full burden. It only lists actions but does not disclose behavioral traits such as side effects (e.g., closing a tab loses state), prerequisites (e.g., index required for switch/close), or authorization needs. The actions are named but their exact behavior is vague.

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 extremely concise (one line). While concise, it sacrifices clarity and structure. A list of actions without elaboration is too terse to be fully helpful, but it does front-load the key 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?

The description lacks details about return values, prerequisites, and action-specific behavior. For a tool with 3 parameters and multiple actions, this is insufficient. No output schema or annotations exist to compensate.

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 input schema has 0% description coverage, and the tool description does not add meaning beyond the schema. The description lists actions but does not explain the roles of 'url' and 'index' parameters, leaving ambiguity about which actions require them.

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 'Manage browser tabs: list, new, close, switch.' It specifies both the resource (tabs) and the actions, distinguishing it from sibling tools like browser_navigate or browser_click.

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?

No guidance is provided on when to use this tool versus alternatives. For example, there is no mention that browser_navigate is for changing the current tab's URL, while browser_tabs with action 'switch' changes the active tab. The description lacks context for when to use each action.

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