navigate

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

With no annotations, the description carries the full burden and does so thoroughly: it cleans script/svg tags, prefixes HTTP status line to avoid misinterpretation of 404/500, honors timeout_ms, wait_for parameters, and prepends a 'bot-challenge page' warning. All key behavioral traits are disclosed beyond what the schema shows.

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 fairly long but every sentence adds value. It is front-loaded with the primary purpose, then covers important edge cases. No filler, but it could arguably be tightened. However, given the complexity of navigation, the length is warranted.

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 main pitfalls in navigation: HTTP error statuses, client-side rendering, and bot detection challenges. With an output schema present, return values need not be explained. This is a complete description for a navigation tool with no annotations.

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 description coverage is 0%, so the description must explain parameters itself. It does: timeout_ms overrides default 30s, wait_for_selector waits for a CSS selector, wait_for_idle waits for network quiet. URL is obvious from 'Go to a URL'. This fully compensates for the lack of schema descriptions.

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 verb ('Go to a URL') and resource ('return the page content'). It also distinguishes from siblings: open_browser opens the browser, get_page_content likely returns current page, while navigate actually changes URL and returns content. The scope is specific.

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 gives clear contextual use guidance: it explains when to use wait_for_selector vs wait_for_idle for client-side rendered sites, and notes the default timeout override. It does not explicitly name alternative tools, but the usage context is clear enough for an agent to understand when to invoke navigate and how to handle different scenarios.

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