browser_new_identity

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

Given no annotations, the description carries full burden. It discloses that a new session is created with a randomized fingerprint and isolated storage, and explains proxy pairing and persistent modes. It also states the return value. However, it omits potential side effects or failure 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 and well-structured, front-loading the main purpose and adding details in a logical order. Every sentence contributes meaningful information with no redundancy.

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?

For a tool with 7 parameters, no required fields, no output schema, and no annotations, the description covers the core functionality and most parameters but misses 'label' and 'no_proxy'. It does not mention error handling or return format beyond stating it returns session info. Completeness is adequate but not thorough.

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?

With 0% schema description coverage, the description must explain all parameters. It explains proxy_url, proxy_server, persistent, and hints at proxy_username/password, but does not cover 'label' or 'no_proxy'. The explanation adds value beyond the schema for some parameters but remains incomplete.

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 fresh browser identity with a novel randomized fingerprint, isolated storage, and optional proxy pairing. It distinguishes itself from sibling tools like browser_new_session and browser_set_proxy by detailing unique features such as fingerprint randomization and persistent profiles.

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 provides clear context on how to use the tool, including default proxyless behavior and options for proxy pairing and persistence. However, it does not explicitly state when to use this tool versus alternatives or provide exclusions.

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