browser_session_switch

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

No annotations are provided, so the description carries full responsibility. It mentions the effect on subsequent tools but does not disclose behavioral traits like what happens to the previous session, whether the switch is reversible, or if there are any side effects. This is insufficient for full transparency.

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 only two sentences, front-loading the core purpose and the consequence of the switch. Every sentence adds value, with no redundancy or fluff.

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 tool with two parameters, no output schema, and no annotations, the description covers the primary action and its impact on future tool calls. It does not explain parameter meanings, but the schema covers that. It is fairly complete but could mention what happens if the session doesn't exist.

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%, with parameters 'name' (required) and 'sessionName' (optional alias). The description adds no additional meaning beyond the schema, as it does not explain the distinction between the two or provide use-case-specific guidance. Baseline 3 is appropriate.

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 it switches the active browser session, and the purpose is distinct from sibling tools like browser_session_create (create) and browser_sessions (list). The verb '切换' (switch) combined with '活跃浏览器会话' (active browser session) precisely defines the action and resource.

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 implies when to use: to set the active session for subsequent tools that omit sessionName. However, it does not explicitly state when not to use it or mention alternatives (e.g., creating a new session instead). The guidance is present but not comprehensive.

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