browser_restart

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the restart is 'clean' and useful for 'clearing state', which hints at side effects like losing session data. However, it does not explicitly warn that all tabs and sessions will be closed or that cookies/saved state may be lost, which are important for a restart operation. It is not misleading but is not fully transparent about the full extent of state reset.

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 concise, with two sentences that lead with the action and immediately follow with concrete use cases. Every word adds value — there is no fluff or repetition. It is well-structured and front-loaded.

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 parameterless tool, the description covers the core purpose and usage scenarios. However, given the surrounding context (browser session management, cookies, multiple tabs), it omits important caveats like the loss of open tabs and saved sessions. This is a gap that could lead an agent to invoke it without understanding how disruptive a restart is. The description is adequate but not fully complete.

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, so per the rubric the baseline is 4. The description does not need to add parameter semantics, and it does not attempt to. This score reflects the simplicity of the parameterless input 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 clearly states the tool's purpose: to cleanly restart the browser process. It specifies the resource (browser process) and the action (restart), and distinguishes from siblings like browser_closeTab or browser_newTab by targeting the entire process rather than individual tabs. The additional context about freeing memory and recovering from issues reinforces the specific use case.

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 context for when to use the tool: freeing memory, clearing state, or recovering from issues during long-running sessions. It does not explicitly mention when not to use it or alternative tools, but the provided scenarios are specific and actionable, placing it just below the highest bar.

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