chrome_navigate

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

No annotations are provided, so the description must fully disclose behavior. It only mentions navigation to a URL, but omits details like whether it waits for page load, handles redirects, or reports errors. This is insufficient for an agent to predict side effects.

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?

The description is extremely concise: three clear sentences in a structured format. Every word is necessary; no redundant information. It earns its brevity.

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 simplicity and presence of an output schema (describing return values), the description provides minimally viable information. It mentions inputs, output type, and session dependency, but lacks detailed behavior or error handling context.

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 schema has 0% description coverage, so the description must compensate. It explains that 'session_id' comes from 'chrome_open_session' and 'url' is a URL to load, which adds meaningful context beyond the schema's type-only definitions. However, it could specify expected URL format or call behavior.

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') and the resource ('an active Chrome CDP session to a URL'). It distinguishes from sibling tools like 'chrome_click' or 'navigate_safari' by specifying Chrome CDP context.

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 does not provide any guidance on when to use this tool versus alternatives, prerequisites (e.g., needing an active session from 'chrome_open_session'), or scenarios where it should be avoided. It only states inputs and outputs.

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