restart_chrome

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

Disclosed side effects (destructive, terminates tabs, closes debugging connection) and prerequisites (CHROME_PATH). No annotations provided, so description carries full burden—well handled.

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?

Concise but includes some redundancy (e.g., side effects list). Front-loaded with main action, but could be slightly tighter.

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?

Covers purpose, alternatives, prerequisites, side effects, and return value. No output schema needed; sufficient for a restart tool with one optional param.

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?

Only one parameter, 'proxy_server', with 100% schema coverage. Description adds no extra meaning beyond the schema's detailed constraints and defaults.

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?

Clearly states it stops and restarts Chrome with remote debugging, optionally configuring proxy. Distinguishes from siblings like 'reload' and 'navigate'.

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?

Explicitly says when to use (reset state, apply proxy, recover from crashes) and provides alternatives ('reload', 'navigate').

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