browser_navigate

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

Discloses that it returns a compact snapshot with ref IDs and eliminates the need for an additional snapshot call. Lacks explicit mention of potential side effects like losing browser state, but this is reasonable for a navigation tool.

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?

Extremely concise: a short sentence for purpose, a behavioral note, return value description, and an Args list. Every sentence serves a clear purpose with no redundancy.

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?

Covers all necessary context for a 2-parameter tool with an output schema: ordering constraint, return behavior, and parameter listing. No gaps for typical usage.

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 0% description coverage for parameters. The description only lists the argument names without adding meaning (e.g., URL format or session_id behavior). This insufficiently compensates for the schema's lack of parameter details.

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 to a URL') and the resource. It distinguishes from siblings by noting it must be called before other browser tools, which is explicit and specific.

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?

Explicitly says 'Must be called before other browser tools,' providing clear when-to-use guidance. Also advises against calling browser_snapshot separately, which is a direct alternative exclusion.

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