select_page

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

The description discloses that index takes precedence, which is important for understanding behavior. However, it fails to mention what happens if no tab matches, how selection interacts with the current page, or whether any side effects occur (e.g., focusing the tab). Since no annotations are provided, the description carries full burden and is only partially adequate.

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, focused sentence that front-loads the core purpose. Every word is necessary; there is no redundancy or extraneous information.

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 selection tool with no output schema and three optional parameters, the description covers the basic functionality. However, it lacks details about selection behavior when multiple matches occur, error handling, or return value, leaving some ambiguity. Overall, it is minimally complete but not comprehensive.

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 provides detailed descriptions for all three parameters (index, URL, title). The description adds the insight that index takes precedence, which clarifies the parameter interaction. With 100% schema coverage, the description's added value is minimal, meeting the baseline of 3.

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 ('select'), the resource ('active tab'), and the methods (by index, URL, or title). It distinguishes from sibling tools like close_page or navigate_page by focusing on selection rather than modification or navigation.

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 provides no guidance on when to use this tool versus alternatives such as navigate_page or list_pages. It mentions precedence among parameters but does not explain the context for using select_page over other tab management tools.

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