browser.activate_tab

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only states the basic action. It does not mention side effects, error handling (e.g., invalid index or session), or whether the action is safe or destructive, leaving significant gaps.

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, concise sentence, which is front-loaded and direct. However, it sacrifices necessary detail for brevity, making it only marginally acceptable.

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 lack of output schema, annotations, and low schema coverage, the description should provide more context about return values, success/error conditions, and constraints. It falls short, leaving the agent with insufficient information to use the tool correctly.

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 description does not add meaning beyond the parameter names 'session_id' and 'index'. The schema has 0% description coverage, so the tool description should compensate, but it fails to specify crucial details like the index being 0-based (implied by schema minimum 0) or the format of session_id.

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 the action (switching) and the resource (active session page to a tab index), making the purpose understandable. However, it does not differentiate from sibling tools like 'browser.close_tab' or 'browser.list_tabs', lacking clarity in context.

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, such as 'browser.close_tab' or 'browser.create_session'. There are no prerequisites, exclusions, or context for appropriate invocation.

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