browser_navigate

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the agent knows this mutates page state against an external network. The description adds the useful behavioral detail about waiting for load and scheme normalization, but doesn't discuss what page state is lost on navigation or failure behavior.

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?

Two short sentences, front-loaded with the primary action, with no filler. The scheme-normalization note earns its place as a common gotcha, though it does overlap with the schema.

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 three-parameter navigation tool with no output schema and annotations carrying the safety profile, the description covers the action, the load semantics, and URL handling. Nothing essential to calling it correctly is missing.

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%, so the url, wait enum, and snapshot parameters are already fully documented in the schema. The description's 'example.com gets https://, localhost:3000 http://' restates the schema's own note ('a bare host gets https://') rather than extending it, so baseline 3 applies.

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 states a specific verb and resource ('Open a URL in the active tab and wait for it to load'), which is unambiguous about what the tool does. It doesn't explicitly name a sibling or contrast itself with browser_tabs/browser_snapshot, so it lands just short of a 5.

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?

Mentioning 'the active tab' implies when this is the right tool (navigating the current tab rather than managing tabs), but no explicit when-to-use/when-not-to-use guidance or alternative is given. An agent must infer that browser_tabs handles tab creation or switching.

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