Navigate

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

With only readOnlyHint=false and openWorldHint=true declared, the description usefully adds the failure mode ('fails with the network error when the page cannot be loaded') and the post-redirect return values. It omits meaningful side effects an agent should know: that navigation discards current page state, that in-flight requests/dialogs may be aborted, and how the timeout behaves on a hang.

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?

Three short sentences with the primary action front-loaded, then return contract, then error contract – a clean priority order with no filler.

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?

No output schema exists, and the description compensates by naming exactly what comes back (final URL after redirects, title, HTTP status) and the error condition. Combined with a fully annotated schema, an agent has everything needed to call it and interpret the result.

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 description coverage is 100%, so url/action mutual exclusion, timeoutMs, waitUntil and ignoreCache are already fully documented in the schema. The description's only additive nuance is 'final URL (after redirects)', which concerns the return value rather than the parameters; 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?

States a specific verb and resource ('Navigates the tab to a URL') plus the alternative modes (back/forward/reload), so the core action is unmistakable. It does not, however, distinguish itself from the sibling tab_open or explain how it relates to wait_for, leaving the boundary between 'navigate existing tab' and 'open new tab' implicit.

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 implies usage through the url-vs-action split, but never states when an agent should pick this over tab_open, tab_select, or a follow-up wait_for. There is no explicit when-not guidance or prerequisite (a tab must exist / be selected) called out in the description itself.

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