browser_navigate

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

Annotations provide readOnlyHint=false, consistent with navigation. Description adds value by mentioning BiDi listeners are kept active, which is a behavioral trait beyond what annotations convey. No destructive or permission details, but acceptable given simplicity.

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?

A single sentence of 12 words that front-loads the action and essential context. No unnecessary information.

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?

For a simple one-parameter tool with an output schema, the description covers the key aspects: action, session scope, and listener preservation. No gaps detected.

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?

Input schema has 100% coverage for the single 'url' parameter with description 'URL to navigate to'. Description simply restates 'Navigate to a URL' without adding new meaning or constraints. Baseline 3 is appropriate.

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?

Description clearly states 'Navigate to a URL in the existing session', which is a specific verb+resource. It distinguishes from browser_open (new session) and navigation siblings like browser_back/forward/refresh by emphasizing 'existing session' and 'keeps BiDi listeners active'.

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 implies when to use (existing session, keep listeners) but does not explicitly state alternatives or when not to use. The context and sibling names give enough clues for an AI agent to infer appropriate usage.

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