navigate

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

With no annotations, the description fully informs about key behaviors: automatic escalation to headless browser for JavaScript-heavy pages, output format conversions with token savings, and inclusion of a YAML accessibility tree. This level of detail is exemplary.

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 well-structured and front-loaded with the main action. While it is relatively long, every sentence provides essential context, so it earns its keep. A slight trim could improve conciseness, but it remains effective.

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 tool's complexity (auto-escalation, multiple output formats, depth controls, page_map), the description covers all aspects comprehensively. It explains defaults, edge cases, and the returned structure (prose + accessibility tree) despite lacking an output schema.

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 already covers all 5 parameters, but the description enhances understanding by explaining real-world implications (e.g., fit_markdown saves ~40% tokens, auto-escalation based on JS indicators, and practical guidance like using 'markdown' if fit_markdown misses content). This adds significant value beyond the schema.

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 purpose: 'Navigate to a URL and return the page content...' with specific output formats. It also distinguishes itself as the 'primary tool for accessing any web page,' setting clear expectations among sibling tools.

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 advises to use this as the primary tool for web page access, and implies that other sibling tools (like click, fill) are for interactions after navigation. However, it does not explicitly state when not to use this tool or provide direct comparisons to alternatives.

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