new_identity

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

Annotations declare this mutates state without being marked destructive; the description adds the key behavioral fact that the browser restarts, plus the non-obvious override of a persistent profile's pinned seed. It stops short of saying what the restart loses (session, cookies), which is the main side effect an agent should know about.

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 short sentences with the primary behavior front-loaded and no filler. The trailing clause 'while it is set' is slightly ambiguous about where the seed is set, costing a bit of crispness.

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?

With no inputs and an output schema present, the description covers the essentials: what changes, that it restarts, and the seed-override interaction. What is missing is the consequence of the restart on existing session state.

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?

The tool takes zero parameters, so the schema carries little burden and the baseline is 4. The mention of an 'explicit seed' relates to profile config rather than an argument here, so there is nothing more the description needs to add.

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 gives a specific action and resource: generate a fresh browser fingerprint from a new random seed and restart the browser. It is distinct from rotate_proxy/fingerprint_info by implication (fingerprint vs. proxy vs. inspection), but does not explicitly name or contrast with those siblings.

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?

'Use after a block' gives a clear triggering condition for when to call it. There is no explicit guidance on when NOT to use it (e.g., versus rotating a proxy after a block) or what prerequisites exist.

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