restart_chrome

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 thoroughly describes side effects ('destructive - terminates running Chrome process and all open tabs; closes debugging connection'), prerequisites, return values ('restart success confirmation'), and use cases. This goes well beyond what the input schema provides.

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 efficiently structured with clear sections: action, side effects, prerequisites, returns, use cases, and alternatives. Every sentence earns its place by providing essential information without redundancy. It's appropriately sized for a tool with significant behavioral implications.

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 tool's complexity (destructive operation with side effects), no annotations, and no output schema, the description provides complete context. It covers purpose, usage guidelines, behavioral transparency, parameter context, prerequisites, and alternatives. The agent has all necessary information to use this tool correctly.

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 100%, so the baseline is 3. The description adds value by mentioning 'optionally configuring proxy' which gives context for the proxy_server parameter, and it explains the purpose ('apply proxy settings') which helps understand when to use this parameter. However, it doesn't provide additional semantic details beyond what's in the schema description.

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 specific action ('stops and restarts') on the specific resource ('managed Chrome instance with remote debugging enabled'), distinguishing it from siblings like 'reload' (refresh page without restart) and 'stop_chrome' (just stops). It explicitly mentions configuring proxy as an optional feature.

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 provides explicit guidance on when to use this tool ('to reset browser state, apply proxy settings, recover from crashes') and when not to use it (alternatives: 'reload' to refresh page without restart, 'navigate' to load new content). It also specifies prerequisites (CHROME_PATH environment variable or chrome in PATH).

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