enable_proxy_auth

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

No annotations provided, so description carries full burden. It lists side effects (background event listener, auto-termination after 30s, pre-warming navigation), auth requirements, prerequisites, and rate limits (30-second timeout). Comprehensive disclosure.

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?

Description is a single paragraph with multiple key points front-loaded. It is clear and no wasted words, though slightly dense but still effective.

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 no output schema, description includes return value. Covers prerequisites, side effects, rate limits, alternatives. Explains when to use and dependencies. Complete for a tool that activates proxy auth.

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 coverage is 100% with good schema descriptions. Description adds context about username and password being sent to proxy server on auth challenge, adding value beyond schema. Does not elaborate on prewarm_url or resource_type but schema covers 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?

The description clearly states the tool activates proxy authentication interception via Fetch domain with credentials. It distinguishes from siblings by specifying when to use (after restart_chrome) and mentioning alternative manual 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?

Explicitly states usage: after restart_chrome with proxy settings. Provides alternative: manual proxy configuration. Also mentions prerequisites (Chrome started with proxy-server flag), giving clear when-to-use guidance.

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