Use temporary profile

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

Beyond the destructiveHint annotation, the description discloses concrete side effects: 'Restarts the browser and closes all open pages' and 'Anything held in the outgoing temp profile is gone.' It also clarifies that the profile being left is not deleted, adding nuance to the destructive behavior and explaining the concurrency benefit.

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 three short paragraphs, front-loaded with the core purpose and followed by lifecycle and side-effect details. Every sentence adds valuable context without repetition or filler.

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 zero-parameter schema and existing output schema, the description covers the tool's lifecycle, concurrency benefit, side effect of restarting, and the critical contrast with persistent profiles. No essential behavioral aspect appears missing.

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 has zero parameters (schema coverage 100% with empty properties), so the description does not need to compensate for undocumented arguments. The baseline of 4 applies because no parameter semantics are required.

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 uses a specific verb 'Switch back' and names the resource 'fresh ephemeral profile' with lifecycle details ('created and deleted per session'). It clearly distinguishes from sibling use_profile by explaining that a persistent one keeps its cookies for the next use_profile.

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?

It states 'This is the default' and explains that it leaves nothing behind, enabling concurrent nodriver instances without profile collisions. It implicitly contrasts with use_profile by describing the persistent profile's cookie retention, giving the agent enough context to choose between them, though it does not explicitly enumerate when-not-to-use scenarios.

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