chrome_select_tab

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. It only states the action without mentioning side effects, error handling for invalid indices, or whether the switch triggers navigation/loading. Minimal transparency.

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?

Description is a single sentence with no fluff: 'Switch to a tab by index (from chrome_list_tabs)'. Every word earns its place, making it highly concise.

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 one-parameter action, the description plus schema provide the essentials (what and how). However, absence of behavioral context (e.g., what happens if index is out-of-range) and lack of annotations make it slightly incomplete.

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 coverage is 100% with index described as 'Tab index (0-based)'. The description adds the source of the index ('from chrome_list_tabs'), but this is marginal beyond what the schema already provides, so baseline 3 is appropriate.

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 specific verb 'Switch' with a resource 'tab' and method 'by index', clearly distinguishing it from sibling tools like chrome_close_tab (closing) or chrome_list_tabs (listing). The reference to chrome_list_tabs further clarifies scope.

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 phrase 'from chrome_list_tabs' implies a prerequisite (list tabs first to get index) but does not explicitly state when to use this tool vs alternatives or when not to use it. Context is implied but not fully developed.

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