fingerprint_rotate

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

With no annotations, the description reveals that the override is applied via CDP and persists until tab creation. It does not disclose side effects, reversibility, or what happens if no parameters are set. The behavior is partially transparent.

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 two sentences plus a fragment, highly efficient with no extraneous words. It front-loads the key action and then adds implementation details, making it easy to scan.

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?

Although an output schema exists, the description omits important context: whether parameters are optional, default behavior when all are null, error scenarios, and whether the override is additive or replaces all fingerprints. This leaves gaps for a mutation tool.

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 0%, yet the description only lists parameter names with a single example for timezone (Asia/Jakarta). It does not specify formats, allowed values, or constraints for user_agent, accept_language, or platform, leaving the agent to infer from names.

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 overrides fingerprint vectors for the active tab, listing the specific parameters (user_agent, accept_language, platform, timezone). It distinguishes itself from sibling tools by specifying scope and persistence, so purpose is explicit and unique.

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 explains that the override is applied via CDP and persists until next tab creation. However, it does not provide guidance on when to use this tool versus alternatives, nor does it mention prerequisites or typical use cases like anti-detection.

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