Navigate

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

The description adds important behavioral nuance beyond the annotations: 'A status of 200 does not prove the real page loaded: bot challenges and interstitials return 200 too, so check the title and snapshot for the expected content before repeating a submission.' It also discloses session-start-on-first-use behavior and the snapshot row limit. No contradiction with the annotations.

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 with the core operation and return payload, then moves to usage guidance, session behavior, and caveats. Every sentence earns its place, and the length is justified by the tool's complexity.

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?

Despite having no output schema, the description explains the return fields (final url, HTTP status, navigated, snapshot). It covers alternatives, session semantics, verification pitfalls, and snapshot limits. For a tool with six parameters and several sibling tools, this is remarkably 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?

The input schema already covers all parameters with detailed descriptions (100% coverage), so the baseline is 3. The description adds value by clarifying the snapshot limit ('up to 300 rows') and reinforcing the url/go mutual exclusivity and the default-session behavior, pushing it above baseline.

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 uses a specific verb and resource: 'Open a URL in the session's active tab (or go back, forward or reload) and return where it landed.' It also names surfsky_scrape and surfsky_act, making clear this is the navigation tool for interactive pages, not the cheap read-only scrape path.

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?

It explicitly says when to use this tool: 'Use it for a page that needs clicks, scrolling, a form or a login; for a page you only need to read once, surfsky_scrape is cheaper and starts no session.' It also gives context on the default session and points to surfsky_snapshot when the 300-row snapshot limit is exceeded.

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