browse_session_navigate

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

The description adds no behavioral context beyond what the annotations already imply. It does not disclose that navigation may trigger side effects (annotations indicate readOnlyHint=false), what happens to the session, or that it may encounter CAPTCHAs. The parameter descriptions cover some behaviors, but the description itself is nearly a restatement of the tool name.

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 a single concise sentence, free of filler or redundancy. It is front-loaded and immediately states the core purpose. While very brief, this dimension rewards conciseness, and the sentence earns its place.

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 a rich schema with 8 parameters and an output schema, the tool description is a single sentence that does not provide an overview of the tool's capabilities, such as returning page content, supporting selectors, or handling CAPTCHAs. It fails to place the tool within the session lifecycle or explain its relationship to sibling tools, leaving the agent without sufficient context for correct invocation.

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 100%, so the baseline is 3. The description itself provides no parameter information, but the schema's detailed parameter descriptions fully document the URL, timeout, selector, output mode, and other options. No additional parameter semantics are needed.

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 action ('Navigate') and the resource ('an existing browser session'), which distinguishes it from session start/close tools. However, it does not explicitly differentiate from the sibling 'browse' tool, which could also imply navigation, so it lacks full sibling differentiation.

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 no guidance on when to use this tool versus alternatives. It does not mention prerequisites (e.g., an existing session from browse_session_start), exclusions, or any comparison to other browsing tools. The agent receives no usage context beyond the tool's name.

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