wrave_open_tab

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the core action but does not mention side effects such as whether the new tab becomes active by default, whether an invalid URL causes an error, or whether any tab reference is returned. Some activation behavior is recoverable from the schema's 'activate' parameter, but the description itself is minimal.

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 filler. Every word contributes to the meaning, and it is appropriately sized for a simple tool.

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?

This is a low-complexity tool with a fully documented schema, so the description plus schema are largely sufficient for correct invocation. It is slightly incomplete only because it does not describe activation behavior or return value, but no output schema exists and the parameter schema covers the main invocation details.

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 100%, with both 'url' and 'activate' documented. The description adds no extra parameter semantics beyond restating that a URL is opened, so the baseline score of 3 is appropriate.

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 uses a specific verb and resource: 'Open a new tab with the specified URL.' The word 'new' distinguishes it from sibling tools like wrave_focus_tab, wrave_close_tab, and wrave_reload_tab, so an agent can clearly tell what this tool does.

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?

The description implies the tool should be used when a new tab needs to be opened, but it gives no explicit guidance about when not to use it or when to prefer a sibling tool such as wrave_focus_tab for an existing tab. Usage context is clear but alternatives are not discussed.

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