activate_tab

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

Annotations already indicate readOnly=false, destructiveHint=true, and idempotent=false. The description adds useful context about foregrounding and focusing, but it does not explain why the operation is marked destructive or what side effects may occur beyond bringing the tab forward. No contradiction with annotations, but the description does not enrich the destructive behavior disclosure.

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 two concise sentences, front-loads the core behavior, and adds usage guidance without any filler. Every clause earns its place.

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 simple single-parameter tool and existing output schema, the behavioral description is reasonably complete for the operation itself. However, the complete lack of session_id documentation leaves a hole in the agent's ability to call the tool correctly in multi-session contexts.

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% for the only parameter, session_id, and the description does not mention it at all. Since the description must compensate for the missing schema documentation, this is a significant gap: the agent receives no guidance on what session_id means or how to populate it.

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 a specific action ('Bring a tab to the foreground and focus its window') and names the tool's relationship to switch_tab. It is easy to distinguish from the sibling switch_tab tool by reading the description alone.

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 explicitly tells the agent when to use this tool: after switch_tab when foreground work is required, or to re-raise a tab the user has clicked away from. This provides concrete usage conditions and an implicit contrast with the switch_tab alternative.

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