browser_goto

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

No annotations present, so description must carry behavioral burden. It fails to disclose critical details like page load wait behavior, timeout handling, error scenarios, or whether navigation is synchronous. Only states the action and return values.

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?

One sentence with zero wasted words. Front-loaded with the action and result. Excellent conciseness.

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 no output schema, the description is minimally adequate. However, it omits important contextual details like error handling, prerequisites (e.g., browser must be initialized), and interaction with other tools. Given sibling complexity, more context would be beneficial.

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% (one parameter with description). The tool description does not add additional meaning beyond what the schema already provides (e.g., URL format requirements are implied but not specified). Baseline at 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 the verb 'Navigate' and the resource 'URL', and mentions the return values (page title and URL). It distinguishes this tool from siblings like browser_back or browser_eval as the primary navigation action.

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?

No guidance on when to use this tool versus alternatives (e.g., browser_back for backwards navigation). The description does not provide any use cases or exclusions.

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