navigate

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

With no annotations, the description carries the full burden of behavioral disclosure. It explicitly states that the tool automatically passes WAAP/anti-bot challenges, dismisses common cookie/consent banners, and returns a specific indexed line format. This goes well beyond a generic 'open URL' statement and gives the agent useful expectations about side effects and output.

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 compact and front-loaded: purpose, behavioral traits, output format, and optimization tip appear in a logical order. Every sentence earns its place, with no filler or redundant restating of the tool name.

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 output schema exists and the description already covers output format, automation behaviors, and the include_snapshot option, an agent has enough context to invoke navigate correctly and decide whether to call snapshot later. Combined with sibling names, this is a complete and self-sufficient definition.

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 compensate. It explains include_snapshot meaningfully ('compact summary', 'saves tokens', 'call snapshot() when you need the list'), while url is self-explanatory. This adds semantic value beyond the schema, though the description does not dive into URL formatting or error cases.

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 opens with a specific verb and resource: 'Open a URL and return an indexed snapshot of the page's interactive elements.' It clearly distinguishes this tool from siblings like fetch, read, and screenshot by emphasizing the indexed snapshot and the automatic handling of WAAP/anti-bot challenges and banners.

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 provides clear context for when to use the snapshot output ('use the index with click / type_text') and how to choose between a full snapshot and a compact summary ('Pass include_snapshot=false... call snapshot()'). It does not explicitly contrast navigate with siblings like fetch or read, but the usage context is well implied and actionable.

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