browser_tab_open

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

No annotations provided. The description mentions reusing a tab by name but doesn't specify behavior when no URL is provided or what happens to the previous tab content. Side effects are unclear.

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 very short (two sentences) but omits important information about the 'name' reuse mechanism and viewport parameter.

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 no output schema and only 2 parameters, the description fails to explain how to specify a tab name for reuse, what the tool returns, or default behavior for optional parameters.

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 value beyond the schema for 'url' (schema already says 'URL to navigate to'). The 'viewport' parameter is not described at all, despite being a nested object with no schema descriptions.

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 states 'Open a browser tab, optionally navigating to a URL' which is clear, but it also says 'Reuses existing tab by name' without a 'name' parameter in the schema, causing confusion about how the reuse works.

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 siblings (browser_tab_close, browser_tab_run) or when to avoid it.

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