select_page

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

No annotations are provided, so the description must disclose behavioral traits. It states 'Select active tab' (mutation) but does not describe what happens if no tab matches, whether the operation is reversible, or if it affects page state. The lack of detail on error handling or side effects makes this insufficient for a tool with no annotations.

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, efficient sentence that front-loads the verb and resource. It has no wasted words. However, it could be slightly expanded to include a second sentence about usage context without harming conciseness.

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 that there is no output schema and all parameters are optional, the description fails to explain default behavior (e.g., what happens if no parameters are provided) or how multiple matches are resolved beyond precedence. Critical behavioral details are missing, making the description incomplete for reliable agent selection.

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 has 100% coverage with descriptions for each parameter. The description adds value by stating 'Index takes precedence,' which clarifies ordering when multiple parameters are provided. This goes beyond the schema but could be more explicit about matching behavior (e.g., if URL and title both match different tabs).

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 tool selects the active tab by three specific criteria (index, URL, title) and explicitly declares precedence (index takes priority). This distinguishes it from sibling tools like 'list_pages' (which lists tabs) and 'navigate_page' (which navigates within a tab).

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 mentions precedence but does not provide explicit guidance on when to use this tool versus alternatives, nor does it list exclusions or prerequisites. Usage context is only implied through the action description.

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