navigate_page

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

The description adds the useful detail that the project URL is used if none is specified. However, it does not disclose other behavioral aspects such as handling of beforeunload dialogs or timeout behavior, which are only in the schema. With readOnlyHint=false, the mutating nature of navigation is implied but not elaborated.

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 a single, concise sentence that is front-loaded with the main action and includes a useful default behavior note. Every word earns its place.

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 the rich schema covering all parameters and the simple navigation task, the description is complete enough. It could mention how this differs from opening a new page (new_page), but the core behavior and scheduling are adequately covered.

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?

The schema covers all 6 parameters with descriptions, so the baseline is 3. The description adds value by clarifying that the URL parameter is optional and defaults to the project URL, which is not explicitly stated in the schema property description.

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 function with specific verbs and resources: 'Go to a URL, or back, forward, or reload.' This distinguishes it from sibling tools like click or new_page, and it also notes the default behavior of using the project URL.

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 clear context for when to use this tool (navigation) and specifies the default URL behavior if none is provided. It does not explicitly exclude alternatives or compare to siblings like new_page, but the task is distinct enough that it is easily understood.

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