navigate

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

With no annotations, the description carries full behavioral burden. It discloses automatic protocol prefixing ('https://'), waits for the initial HTML document, and notes that navigation adds to browser history. Minor omissions like error handling or timeout behavior slightly reduce completeness, but core behavioral expectations are well covered.

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 well-organized with clear sections for Args, Returns, and Tool selection. It front-loads the primary purpose and usage. The only blemish is a likely typo in the tool selection section where 'forward' is mapped to 'reload' instead of 'forward', which slightly detracts from an otherwise crisp structure.

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 single-parameter tool with an output schema, the description covers all essential aspects: what URL formats are accepted, protocol handling, loading behavior, return confirmation, and clear alternative routing. It is fully sufficient for an agent to select and invoke navigate correctly.

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 0%, so the description must fully explain the url parameter. It does, stating it may be a complete URL or hostname, explaining the automatic 'https://' prefix with a concrete example. This adds substantial meaning beyond the bare schema definition.

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 opens with 'Navigate the current browser tab to a URL,' a specific verb+resource statement. It further distinguishes the tool from history-based navigation by stating it is for visiting a new URL 'rather than move through its existing back/forward history,' clearly differentiating it from sibling manage_history.

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 provides explicit selection guidance: use navigate for a new URL, manage_history for back/forward/reload. It names the exact alternatives and their actions ('manage_history(action="back")'), leaving no ambiguity about when this tool should be chosen.

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