set_proxy

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

No annotations are provided, so the description carries the full burden. It discloses two important behavioral traits: an empty string disables the proxy, and in serve-mode the browser restarts with the new proxy. This is meaningful transparency beyond a simple 'set proxy' statement.

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 extremely compact yet information-dense. Every sentence carries useful operational details: format, disable behavior, and serve-mode side effect. No filler or repetition.

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 simple one-parameter tool, the description covers what to pass, how to disable, and key runtime behavior. It omits details about error handling or effect on the currently active browser session, but the output schema exists and the tool complexity is low, so it is sufficiently 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 schema describes only one parameter 'proxy' with a default value, and schema description coverage is 0%. The description compensates by documenting valid value formats ('host:port', 'user:pass@host:port', 'socks5://host:port') and the empty-string meaning. The format list is illustrative rather than exhaustive, so it is not a perfect 5.

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 identifies the action ('set proxy') and the resource, with specific format examples and an explicit 'turn off' case. This set_proxy tool is clearly distinguished from all sibling tools, none of which target proxy configuration.

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 useful context: it is a runtime change, the method of passing the proxy value, and the special server-mode behavior. It does not explicitly say 'when not to use it', but there are no competing proxy tools among the siblings, so the usage is sufficiently clear.

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