navigate

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

No annotations are provided, so the description carries full burden. It discloses automatic escalation from HTTP fetch to headless browser when JavaScript rendering is detected (React, Next.js, etc.), and mentions the embedded page_map. This adds important behavioral context beyond the schema.

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 three sentences, front-loaded with the main verb+resource. It efficiently packs behavior and parameter guidance without redundancy. However, it is slightly dense; a more structured list could improve readability.

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 5 parameters with full schema coverage and no output schema, the description covers the main return types (content with page_map) and key behavioral traits (automatic upgrade). It could mention error handling or timeouts, but overall it is complete enough for an agent to use effectively.

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 coverage is 100%, so baseline is 3. The description adds value by explaining why fit_markdown exists (token efficiency), when to override format, the purpose of content_depth levels, and strip_images token savings. It goes beyond enum names.

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 navigates to a URL and returns page content in multiple formats. It distinguishes from sibling tools by labeling itself as the primary tool for accessing any web page, while siblings handle interactions like clicking or form filling.

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 explicitly says 'Use this as the primary tool for accessing any web page' and provides guidance on when to choose alternative formats (e.g., 'Use 'markdown' if fit_markdown seems to be missing important content'). It does not explicitly state when not to use it, but context implies it's the first step.

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