browser_rotate_ip

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It only mentions that session state preservation is optional, but fails to disclose potential side effects such as disruption of ongoing browser activity, whether the rotation is immediate or takes time, or whether an active tunnel is required. The tool's behavior beyond the core action is largely opaque.

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 sentence with two short clauses, front-loading the core action and promptly addressing the optional session preservation. Every word earns its place; there is no waste or 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?

Given the lack of annotations and the existence of an output schema, the description is too sparse to fully contextualize the operation. It omits situational context such as prerequisites (e.g., needing an existing tunnel), what the return value indicates, and potential impact on the current browser session beyond cookies/localStorage. The tool appears to be a simple rotation, but the absence of these details leaves the agent under-informed.

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?

Both parameters are already fully described in the schema with 100% coverage: 'slot' is documented as 'CDP slot number currently in use' and 'preserve_session' as 'Save and reload cookies/localStorage across rotation.' The description's phrase 'Optionally preserves session state' adds no new meaning beyond the schema. It does not clarify the cryptic 'slot' parameter, so it adds minimal value beyond the structured 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?

The description states a specific verb and resource: 'Rotate to a new tunnel exit IP.' This clearly distinguishes the tool from sibling tools like browser_use_tunnel or browser_use_tor, which establish a tunnel rather than rotate its exit IP. The action is unambiguous and concisely stated.

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 does not provide any explicit guidance on when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. The only hint is 'Optionally preserves session state,' which indicates a choice about session handling but does not frame when rotation is appropriate or preferred over other IP-related tools.

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