navigate

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

With no annotations, the description carries the full behavioral burden. It usefully explains the waiting semantics of load, dom, and idle, but omits side effects, timeout behavior, and what the tool returns after navigation.

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 front-loaded and compact, with the core action first followed by the key parameter explanation. The phrasing 'wait for it. until:' is slightly awkward but not wasteful.

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?

For a browser navigation tool with no annotations or output schema, the description covers purpose and the most important enum parameter. It still leaves gaps around tab targeting, timeout handling, and post-navigation return behavior.

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 only 50%, and the description compensates partially by explaining the 'until' enum values in richer terms than the schema. However, it does not add meaning for 'tab' or 'timeout', leaving half the parameters undocumented 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?

States a specific verb and resource: open a URL and wait for it. This clearly distinguishes the core navigation action from sibling tools like reload, back, and click, though it does not explicitly name those alternatives.

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 gives useful guidance for choosing the 'until' value, such as 'dom' being fastest and fine for server-rendered pages, but it does not say when to use navigate versus reload, forward, back, or other navigation-related siblings.

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