Select Chrome Tab

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'select the active tab' without detailing side effects (e.g., whether it actually activates the tab in the browser), prerequisites (e.g., where to get tabId), error behavior, or the role of the 'activate' parameter. This is a significant gap for a state-changing tool.

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, direct sentence that gets to the point without filler: 'Select the active tab for subsequent Chromate tools.' It is front-loaded with the action and resource, making it easy to scan.

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?

The tool has 2 parameters, 0% schema description coverage, no annotations, and no output schema. The description only conveys the core purpose but leaves out essential usage details like how to obtain tabId (likely from list_tabs) and what the 'activate' parameter does. The context is too sparse for reliable use.

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 description does not mention either parameter (tabId or activate), and schema description coverage is 0%. Since there are parameters, the description must compensate, but it provides no meaning beyond the raw schema types. The required parameter tabId and optional activate are completely unexplained.

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's function: 'Select the active tab for subsequent Chromate tools.' It uses a specific verb ('Select') and resource ('active tab'), and the phrase 'for subsequent Chromate tools' distinguishes it from sibling tools like list_tabs, page_info, or click, which do different operations.

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 clear context by noting this is for 'subsequent Chromate tools,' implying it should be used before other operations. However, it doesn't explicitly state when not to use it or mention alternatives, so it's not a full 5.

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