browser_switch_page

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

With no annotations, the description must fully disclose behavioral traits. It only states the action but does not mention side effects (e.g., what happens to the previous active page), error scenarios (invalid page_id), or output format despite an output schema existing.

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 sentence, which is concise, but it is under-specified for a tool with two parameters. While there is no verbosity, the lack of structure (e.g., separating parameter explanation) reduces clarity.

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 complexity (2 params, no annotations, and an output schema), the description is too brief. It does not explain the relationship between session_id and page_id, nor does it indicate what the output schema contains or how to handle errors, leaving the agent unprepared 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?

Schema description coverage is 0%, so the description is critical for explaining parameters. It only references 'page ID' but does not define the two required parameters (session_id and page_id) or their purpose, leaving the agent with no additional semantic information.

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 ('switch') and the target ('active page') using a specific identifier ('page ID'). It distinguishes from sibling tools like browser_navigate (URL-based) and browser_new_page (create new page).

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 like browser_navigate, browser_close_page, or browser_list_pages. There is no mention of prerequisites, such as having multiple pages open, or when switching is appropriate.

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