select_page

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

With no annotations provided, the description carries the disclosure burden. It states the core behavior (sets active context) but omits potential side effects, error conditions (e.g., invalid contextId), or confirmation of success. The transparency is adequate but not thorough.

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, well-structured sentence that efficiently conveys the tool's function. No extraneous words or 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?

Despite its simplicity, the description lacks necessary context: it does not explain what 'active browsing context' means, how to retrieve valid contextIds, or what subsequent tools are affected. The absence of an output schema further reduces completeness for agent 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 'contextId' parameter is a string with no schema description. The tool description does not clarify what values are expected or how to obtain them (e.g., from list_pages). Since schema coverage is 0%, the description should compensate, but it adds no additional meaning.

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 ('Set the active browsing context') and the scope ('for subsequent tool calls'). It effectively distinguishes from sibling tools like 'navigate_page' (navigation) and 'select_frame' (frame selection) by focusing on page-level context switching.

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 implicitly suggests using this tool to switch between existing pages but lacks explicit guidance on when to use it versus alternatives like 'list_pages' or 'new_page'. No when-not-to-use or prerequisite information is provided.

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