browser_open_login

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

No annotations provided; description mentions it's an 'advanced compatibility tool' and opens a URL, but does not disclose potential side effects, state changes, or prerequisites beyond the env variable.

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 concise sentences that efficiently convey purpose and usage guidance without wasted words.

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 the simple nature (open a URL) and no output schema, the description covers the core intent and alternative, though it omits explicit mention of return value or confirmation that the action is safe.

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 only parameter (waitUntil) is documented in the schema with enum and default but the description adds no explanation of its meaning or impact, and schema coverage is 0%.

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 opens the remote browser login URL and distinguishes from the preferred alternative sa2_open_target.

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 advises most agents to use sa2_open_target instead, reserving this tool for advanced compatibility scenarios.

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