browser_activate_tab

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

The annotations already say readOnlyHint=false, idempotentHint=false, openWorldHint=true, and destructiveHint=false, so the description needs to explain only the browser focus side effects. It does not say whether the activation steals OS focus, what happens on failure, or that the layout guard can abort the operation; that guard appears only in the schema. It adds nothing beyond the annotations.

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?

It is a single front-loaded sentence with no filler. It is efficient, though arguably too terse for a mutating, non-idempotent action.

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?

With no output schema and 100% schema coverage, the description has a low burden to meet. Still, for a non-idempotent, open-world tool, it does not describe failure behavior, effect on the user's visible window, or the layout verification step. That makes it adequate rather than complete.

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 coverage is 100%, and both parameters (target_id, expected_layout_id) are fully documented in the schema, so the baseline is 3. The word 'exact' reinforces that target_id must be exact, but it adds no detail beyond what the schema already provides.

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?

States a specific verb and resource: bringing a TradingView chart tab to the foreground. It is clearly distinguishable from browser_list_tabs, browser_close_tab, and browser_navigate. However, it does not name which sibling to use when the goal is actually switching panes (pane_focus) or opening a new 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 gives no when-to-use guidance, no prerequisites, and no alternatives. It never says that target_id should come from browser_list_tabs or how this differs from browser_navigate/pane_focus. The only hint is 'this exact ... tab', which implies a precondition but does not state it.

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