Navigate to a URL

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

Annotations provide readOnlyHint=false and destructiveHint=false, so the description adds value by specifying that it resolves on the load event (or SPA history event) rather than a fixed sleep. This discloses the waiting mechanism, which is beyond the annotations. No contradiction.

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?

Two sentences with no redundant information. The first sentence states the action, the second explains the wait behavior. 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 a single required parameter and no output schema, the description covers the essential purpose and the waiting behavior. It doesn't mention error handling or timeouts, but for a simple navigation tool, it is sufficient. The mention of 'page to settle' and load event gives enough context.

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 100% of the parameter with a description 'The URL to navigate to'. The tool description does not add additional semantics about URL format, validation, or relative vs absolute. Since schema coverage is high, the description adds no extra value for the parameter.

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 action ('Navigate to a URL') and the resource (URL). It also specifies the wait behavior, distinguishing it from sibling navigation tools like browser_navigate_back/forward/reload.

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 does not explicitly compare with alternatives, but the name and title make the primary navigation purpose clear. It provides context about waiting for the page to settle, implying it's the main navigation tool. However, it lacks explicit guidance on when to use back/forward/reload.

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