camofox_create_tab

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

No annotations are provided, so the description carries full burden. It discloses the trace parameter constraint (must be set on first tab) and mentions the return value (tabId). However, it does not explain what happens if no session exists, whether a browser is automatically started, or error scenarios.

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: a title line and a short paragraph. It uses clear formatting with a 'PREFERRED' label. Every sentence adds value, though it could be slightly more compact without losing information.

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 5 parameters, no output schema, and no annotations, the description covers purpose, preferred usage, return value, and a key behavioral note about the trace parameter. However, it lacks details on session initialization, default behavior, error handling, and the exact return format, leaving gaps for an agent.

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?

Parameter schema coverage is 100% with descriptions in the schema. The description adds value by noting that 'trace' must be set on first tab creation and that 'listItemId' is a legacy alias for sessionKey. However, for most parameters, the description does not add meaning beyond what the schema already provides.

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 the tool creates a new tab using Camoufox anti-detection browser, and returns a tabId. It distinguishes itself from siblings by emphasizing that Camoufox tools bypass bot detection on sites like Google and Amazon, contrasting with Chrome/the built-in browser.

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 explicitly says 'PREFERRED: Use camofox tools instead of Chrome/the built-in browser' and explains why (bypass bot detection). It provides clear context for when to use this tool, though it does not explicitly state when not to use it beyond implying alternatives.

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