browser_navigate

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

Annotations are absent, so the description carries the full burden. It mentions persistent authentication but does not disclose side effects like page load behavior, potential redirects, or error handling. Some details are implied by the 'waitUntil' parameter, but the description itself offers minimal behavioral insight.

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?

A single, compact sentence conveys the essential action and a key feature. No redundant or irrelevant information; perfectly sized for the simplicity of the tool.

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?

The description is minimal and does not explain return values, error conditions, or whether navigation affects browser state beyond authentication. Given the absence of an output schema and annotations, this leaves some ambiguity for the agent, though the core purpose is clear.

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?

Both parameters (url, waitUntil) are documented in the schema with clear descriptions, achieving 100% coverage. The tool description adds no extra context for parameters, so the baseline score of 3 is appropriate.

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 a specific verb ('Navigate') and resource ('stealth browser') with a target URL, and mentions persistent authentication as a distinguishing feature. It is unambiguous and distinct from sibling tools like clicking or typing.

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?

No explicit guidance on when to use this tool versus alternatives. However, the action is self-explanatory as the primary navigation tool among the siblings, making the intended use implicit. It lacks direct comparisons or conditions.

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