browser_login

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

Describes interactive nature (user must complete OAuth), timeout, and automatic cookie/session saving. Since no annotations exist, the description carries full burden and does so adequately.

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?

Well-structured with header, recommended flow, workflow steps, and args. Some redundancy (e.g., workflow repeats steps), but overall clear and not excessively long.

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 the core process but lacks details on return value format, error conditions, and behavior when login fails. An output schema exists but is not described here.

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?

Adds meaning to both parameters: use_persistent is recommended, timeout unit is seconds with default 300. Schema lacks property descriptions, so description compensates well.

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 launching a browser for login, with explicit steps (open browser, wait for OAuth, save cookies) that distinguish it from sibling tools like check_login_status or clear_saved_cookies.

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?

Provides a recommended workflow (call this tool first, then login, then collect_reports), but does not explicitly exclude alternatives or explain when not to use it.

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