configure_proxy

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

Discloses that the browser restarts and that without user_data_dir a fresh session starts. However, does not mention if the browser must already be running or other side effects like disconnecting pages. No annotations to compensate.

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?

Two efficient sentences, front-loaded with action and purpose. No redundant information.

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 key behavioral aspects (restart, proxy formats, session persistence). Slightly lacks prerequisites (browser running) but output schema exists, reducing need for return value documentation.

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?

Describes proxy_url format in detail and explains user_data_dir's role, adding value beyond the schema. But headless parameter is not mentioned although schema lists it with default false.

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 restarts the browser to route traffic through the given proxy URL. Specifies accepted URL formats and distinguishes from sibling tools like clear_proxy by describing the action.

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?

Implies usage for setting proxy, but does not explicitly say when to use vs alternatives like clear_proxy or mock_response. Provides guidance on user_data_dir for session persistence.

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