navigate

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

With no annotations, the description carries full burden for behavioral disclosure. It lists actions but fails to disclose side effects (e.g., page load time, cache impacts), error behavior, or that navigation changes current page state. The timeout and waitUntil parameters are in schema but not elaborated in description.

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?

The description is extremely concise—two sentences, no redundant information. Every word serves a purpose, with the action listings front-loaded for quick scanning.

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 six parameters (two required) and no output schema, the description lacks details on return values (e.g., info action output), error handling, and dependency on a browser connection (connectionReason required). It feels incomplete for a navigation tool.

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%, so parameters are well-documented. The description adds a list of actions with brief clarifications, but these largely repeat the schema's enum descriptions, offering minimal additional meaning beyond the schema.

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's purpose as navigating and controlling browser pages, and explicitly lists five specific actions (goto, reload, back, forward, info), making it highly specific and distinguishable from sibling tools.

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?

The description implies usage through the listed actions but does not explicitly state when to use navigate versus alternatives like 'content' or 'dom'. No guidance on prerequisites (e.g., browser connection) or when to prefer other tools.

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