navigate_page

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

The description adds meaningful behavioral details beyond the readOnlyHint=false annotation, such as waiting for DOMContentLoaded (not full load) and a 10-second default timeout. This enriches the agent's understanding of the operation's side effects and timing. The annotation is consistent with the tool's mutating nature, so no contradiction exists.

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 two sentences, front-loaded with the core purpose, and every sentence contributes unique information (navigation types, DOMContentLoaded wait, timeout default). There is no redundancy or filler.

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 covers the essential aspects of navigation, including action types and a key timing behavior, and is complemented by a schema with full parameter descriptions. It does not explicitly address error conditions or prerequisites beyond 'currently selected page', but within the context of the tool's complexity and available metadata, it is sufficiently complete.

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?

While the schema covers all parameter descriptions (100% coverage), the description adds the concrete default timeout value (10 seconds), which is not present in the schema. This extra detail helps the agent reason about parameter behavior beyond the structured metadata.

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 ('navigates') and resource ('currently selected page'), and enumerates distinct navigation modes (URL, back, forward, reload). It also differentiates from sibling tools like list_pages and select_page by focusing on navigation actions rather than page listing or selection.

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 establishes when to use the tool ('navigates the currently selected page'), implying a prerequisite of a selected page. It does not explicitly mention alternatives or when not to use it, but the usage context is clear enough for most scenarios.

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