Allocate multiple isolated browser profiles at once, returning one handle per profile so AI agents can run parallel sessions with persistent identities.
The same for several profiles at once, one handle each.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It discloses that one handle is returned per profile, but does not state side effects, authentication needs, rate limits, whether handles must be released, or what 'the same' operation actually entails.
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?
It is a single short sentence, but it is under-specified rather than concise. The phrase 'The same' is not front-loaded or self-contained, forcing the agent to resolve meaning from sibling context.
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 annotations, no output schema, and no parameters, the description must carry nearly all context. It only hints at batch leasing and one handle per profile; it omits how profiles are selected, what a handle is used for, and whether any cleanup is required.
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?
There are zero parameters, so there is no schema parameter information for the description to supplement. The baseline for zero-parameter tools is 4, and the description does not mislead about parameter usage.
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 vague indication of batch operation ('for several profiles at once') and output shape ('one handle each'), but the verb is missing and 'The same' is anaphoric, requiring the agent to infer it refers to lease_profile. It does not clearly state what resource is being leased or distinguish itself explicitly from 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?
It implies use when operating on several profiles at once, but gives no explicit when-to-use guidance, no when-not-to-use conditions, and no named alternative such as lease_profile. The agent must infer that this is the batch version of a single-profile lease.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.