tab_activate

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

No annotations are present, so the description carries the full behavioral burden. It only restates the action; it does not disclose prerequisites, side effects, error behavior, or whether the tab must already exist or be attached to DevTools.

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 one short sentence with no wasted words and the key action is front-loaded. It loses a point only for being too bare to provide the behavioral and usage context needed elsewhere.

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 tool, this is minimally adequate for a straightforward call with a valid tab id. However, it omits the relationship with tabs_list, error behavior, and any output or follow-up expectations, so it is not fully complete.

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 description coverage is 0%, and the description needs to compensate. The phrase 'by id' maps to tabId but adds little beyond the property name and integer type; it does not explain where the id comes from, how it is scoped, or any format concerns.

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 the specific verb 'Activate' with the resource 'Chrome tab' and identifies the selection mechanism ('by id'). This clearly distinguishes it from sibling tools like tabs_list (listing), page_reload (reloading), and devtools_attach (debugging).

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?

There is no when-to-use guidance, no mention of retrieving the tabId from tabs_list, and no exclusions or alternatives. The description leaves the agent to infer the appropriate context for activation.

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