browser_focus_tab

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

No annotations provided, but description fully discloses behavior: it goes through chrome.tabs.update + chrome.windows.update, avoids CDP restriction, activates tab and focuses window. All relevant behavioral traits are explained.

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?

Description is concise and well-structured: first line states purpose, then contrast with sibling, use case, implementation details, and parameter explanation. Every sentence adds value with no redundancy.

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?

Tool is simple (1 param), has output schema, and description covers purpose, usage, behavioral details, and parameter source. Includes sibling differentiation and reasoning for implementation. Complete for its complexity.

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 has single parameter tab_id with no description, but tool description adds: 'The tab ID to focus (from browser_get_tabs).' This provides source context beyond the schema, though minimal. Score slightly below 5 due to brevity.

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?

Description clearly states the tool's action: 'Bring a Chrome tab to the foreground: activate the tab AND focus its window.' It also explicitly distinguishes from sibling tool browser_switch_tab by explaining what this tool does differently.

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?

Provides explicit guidance: 'Unlike browser_switch_tab... this actually makes the tab visible to the user. Use this when the user can't find the tab the agent is working on.' Clearly states when to use and contrasts with alternative.

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