Tabs

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

Without annotations, the description should cover behavioral traits like side effects, session requirement, or zero-based indexing. It only lists actions without revealing how tabs are managed or that 'open' maps to action 'new'.

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?

Single sentence listing all actions, front-loaded and compact. Could improve by aligning 'open' with 'new' but otherwise efficient.

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 22 sibling tools and no output schema, the description lacks critical context about session dependence, action semantics, and when to combine with other tools like browser_create_session.

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 adds no extra meaning beyond the schema; it even creates ambiguity by using 'open' for action 'new'. The optional index parameter is not clarified in context.

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 explicitly states the tool manages tabs (list, open, close, select) which aligns with the action enum and clearly distinguishes from sibling browser tools like browser_navigate or browser_create_session.

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 guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., existing session) or when to prefer other tools like browser_navigate for navigation.

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