Switch To Tab

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

Adds useful behavioral context beyond annotations by explicitly stating that the operation changes what the user sees. This complements readOnlyHint=false and gives the agent a strong reason to avoid calling it unnecessarily, even though it does not detail return behavior.

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?

Two focused sentences with no waste. The first states the core action and outcome; the second adds important usage guidance. Critical information is front-loaded.

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?

For a simple two-parameter UI mutation with no output schema, the description covers the core action, user-visible side effect, and a usage caveat. Minor gaps include not naming the exact preferred reading tool and not describing the return value, but these are not significant for correct invocation.

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 already fully documents both parameters, including tab_id's source ('from list_tabs') and activate's default and meaning. The description adds no additional parameter-level meaning, so the schema carries the burden.

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: 'Make a tab the active tab in its window.' It also differentiates from read-only tab operations by noting it changes what the user sees, so an agent can distinguish it from list_tabs, get_current_tab, and content-reading siblings.

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 a clear when-not condition: prefer reading a tab by id when only content is needed. It does not name the exact alternative tool, but the guidance points toward content-reading siblings like get_page_content or get_html rather than switching UI state.

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