desktop_open_browser

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

No annotations are provided, so the description carries the full burden of behavioral disclosure, and it does so thoroughly. It discloses deletion triggers, dependency requirements, the absence of auto-downloading/profile attachment, and unsupported UI interaction modes. This is exactly the kind of behavioral detail an agent needs to avoid incorrect assumptions.

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 dense but every sentence earns its place: core behavior first, then lifecycle/deletion semantics, then prerequisites and limitations, then interaction constraints. It is front-loaded with the most important decision-relevant information and contains no 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?

For a browser-opening tool with no annotations and no output schema, the description covers prerequisites, lifecycle, and operational limitations well. It does not describe the return value or explicit failure behavior, but those are secondary for this kind of command. Overall, an agent has enough context to invoke it correctly and predict its effects.

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 description coverage is 0%, so the description must compensate for the bare schema. It adds meaningful semantics to the lifetime parameter by explaining that the temporary session is deleted on disconnect, backend close, or reconnect. The url parameter remains simple and predictable from the tool's purpose and schema title, so the lack of extra explanation is not a significant gap.

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 action and resource: "Open a fresh owned Chromium" and immediately specifies the lifetime mode. It also distinguishes the tool from generic launchers by detailing ephemerality and the fact that it never attaches existing profiles. This is clearly differentiated from the sibling automation tools.

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 gives clear usage context: use this for a temporary, disposable browser session with explicit lifetime semantics, and understand that dependencies must already be configured. It does not name a sibling alternative, but no sibling tool appears to be a competing browser opener, so the omission is acceptable. The guidance to inspect text_fields and the list of unsupported operations also helps the agent know what interactions to expect after opening the browser.

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