Activate Chrome tab

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

With no annotations, the description carries the full burden. It adds a useful behavioral trait (focusing the window), but does not disclose error behavior, prerequisites (e.g., tab must exist), or how tab ID is obtained. This is somewhat transparent for a simple UI action, but gaps remain.

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?

A single, compact sentence that conveys the core operation and one important side effect; no redundant words.

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 tool's low complexity and single parameter, the description covers the basic action and effect. However, it omits any mention of where tabId comes from or failure scenarios, making it minimally sufficient but not fully contextual.

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 the `tabId` parameter at all, and schema coverage is 0%. The parameter is self-explanatory from its name and the tool's purpose, but the description adds no semantic detail beyond the schema.

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 action ('Activate'), the resource ('a Chrome tab'), and the additional effect ('focus its window'), distinguishing it from sibling tools like browser_list_tabs or browser_close_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?

It implies usage—activating an existing tab—but provides no explicit when-to-use guidance or alternative references. The intended context is inferable from the tool's purpose, but there is no direct comparison with sibling tools or mention of prerequisites.

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