tabs_activate

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

With no annotations, the description carries the full burden. It states the action but does not disclose side effects, such as changing the active tab, whether it returns any value, or behavior on invalid tabId. For a mutation tool, this lacks important 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?

The description is a single, front-loaded sentence with no extraneous content. It is concise and to the point, achieving high efficiency.

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 tool with one parameter, the description is minimal but does not explain return values (no output schema) or error handling. The agent knows what it does but not what to expect after calling, which is a notable gap.

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 schema already provides full parameter documentation: tabId is described as 'Tab id from tabs_context' with 100% coverage. The description adds no additional meaning beyond the schema, so it meets the baseline of 3.

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 'Bring a tab to the front' clearly states the action and resource. It distinguishes from siblings like tabs_create and tabs_close by implying activation of an existing tab, though it could be more explicit about the 'front' meaning (e.g., active tab in current window).

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?

No explicit when-to-use or when-not-to-use guidance. The description does not mention that this tool is for switching to an existing tab, nor does it compare with alternatives like navigate or tabs_create. The parameter schema hints that tabId comes from tabs_context, but the description itself offers no contextual direction.

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