wavexis_new_tab

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

Annotations indicate readOnlyHint=false, openWorldHint=true, idempotentHint=false, destructiveHint=false. The description adds the behavioral trait of returning a 'tab_id' in JSON, but does not disclose other aspects like whether the tab is active, or any side effects beyond what annotations already imply.

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 concise, with the first sentence stating the purpose, followed by a clear Args/Returns format. It is appropriately sized with no superfluous content.

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 tool (one parameter), the presence of an output schema describing the return value, and adequate annotations, the description is mostly complete. It could mention possible errors or the visibility of the new tab, but it meets the minimum for understanding.

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 coverage is 0%, so the description should compensate. However, it only mentions 'URL' for the input parameter, ignoring the required 'session_id' parameter. The schema provides more detail, but the description fails to add meaning beyond a vague reference.

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 'Create a new browser tab,' which is a specific verb+resource. This distinguishes it from sibling tools like wavexis_close_tab, wavexis_activate_tab, etc.

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 using this tool when a new tab is needed, but it does not provide explicit guidance on when to use this versus alternatives, nor does it mention exclusions or prerequisites.

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