create_tab

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

With no annotations, the description carries the full burden. It discloses that each tab gets a unique fingerprint, and explains the behavior of sharing the CLI context. However, it does not mention what the tool returns, whether it opens a new window, or any potential side effects like rate limits.

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 paragraph of four sentences, front-loading the core action. It is clear and efficient, though a more structured layout (e.g., bullet points for the CLI sharing case) could improve scannability.

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 11 parameters including nested objects and no output schema, the description adequately covers the tool's purpose and CLI context behavior. However, it omits return value information and broader tab lifecycle context, leaving some gap for agent decision-making.

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 100%, so the baseline is 3. The description adds context for userId/sessionKey sharing and viewport usage, but does not introduce new meaning beyond the schema's detailed 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 clearly states 'Create a new browser tab with anti-detection fingerprinting'—a specific verb and resource. It distinguishes from siblings like close_tab and navigate by emphasizing fingerprinting and parameter customization.

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 gives explicit guidance for sharing the CLI default profile using userId 'cli-default' and sessionKey 'default', and notes that this does not attach to an already open CLI tab. However, it does not explicitly compare to alternatives like load_profile or navigate for creating tabs.

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