create_tab

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

Discloses key behaviors: each tab gets a unique fingerprint, optional URL and userId for session isolation, and returns the tab ID. With no annotations, the description carries the burden and does so effectively, though it omits potential side effects like tab limits or resource usage.

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?

Two sentences, front-loaded with purpose, no wasted words. Every sentence adds value: creation, fingerprinting, optional params, and return.

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 and no output schema, the description covers core purpose and return. It could explain the relationship between fingerprinting parameters (e.g., preset vs locale) but the schema descriptions are rich, so it remains mostly complete.

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 baseline is 3. The description adds context that URL and userId are for session isolation, but does not elaborate on other parameters. This slight addition meets the baseline but doesn't significantly enhance understanding beyond the schema.

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?

Clearly states the action 'create a new browser tab' with the specific feature of anti-detection fingerprinting. Distinguishes from sibling tools like close_tab and list_tabs by focusing on creation and unique fingerprints.

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?

Implies use for creating isolated browser tabs with fingerprinting but lacks explicit guidance on when to use this tool over alternatives (e.g., load_profile). No exclusion criteria or context provided.

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