Auto-Browser

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. While 'Switch' implies a state mutation, the description fails to clarify error handling (e.g., invalid index bounds), side effects on the previous active tab, or whether the operation is synchronous/waiting.

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 with the action verb front-loaded. It is appropriately brief, though the phrasing 'to one tab index' is slightly awkward ('to a specific tab index' would be clearer) and 'active session page' could be more precise.

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 0% schema coverage, lack of annotations, and absence of an output schema, the description is insufficiently complete. For a state-changing operation, it should specify parameter constraints (e.g., index bounds), error conditions, or the effect on browser state, none of which are present.

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?

With 0% schema description coverage, the description must compensate. It partially succeeds by referencing 'session' (mapping to session_id) and 'tab index' (mapping to index), providing basic semantic context. However, it does not clarify the 0-based indexing constraint (only visible in schema minimum: 0) or the expected format of session_id.

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 uses a clear verb ('Switch') and identifies the resource ('active session page'), indicating it changes the current view to a different tab. However, it does not explicitly differentiate from siblings like browser.close_tab or browser.list_tabs within the text itself, relying on the tool name for distinction.

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 (e.g., when to switch tabs vs. closing them) or prerequisites (e.g., requiring a valid session_id from browser.create_session). It lacks explicit when-to-use or when-not-to-use conditions.

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