navigate

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

No annotations provided, so description carries full burden. It explicitly discloses side effects ('destructive of current page state; discards unsaved work'), auth requirements (same-origin policy), rate limits (none), and local restrictions, which are beyond basic operation.

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?

Every sentence is necessary: action, side effects, prerequisites, returns, auth, rate limits, usage hint, and alternative. Information is front-loaded and efficiently structured.

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?

Given the tool's complexity (navigation with side effects), one parameter, and no output schema, the description covers all critical aspects: side effects, prerequisites, return type, auth, rate limits, and usage guidance. No gaps.

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?

The single parameter 'url' has 100% schema coverage with detailed constraints and interactions. The tool description does not add new parameter information beyond what the schema provides, achieving the baseline of 3.

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 ('Navigates the current Chrome tab to a specified URL, loading new page content'), identifying the specific verb and resource. It distinguishes from sibling tools by mentioning 'reload' as an alternative.

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 states when to use the tool ('Use this to change the current page') and provides an alternative ('Alternatives: 'reload' to refresh current page'). Also lists prerequisites (active Chrome tab, valid URL).

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