navigate_page

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

No annotations are provided, so the description carries the full burden. It mentions navigation actions but does not disclose that navigation may cause page unload, state loss, or require permissions. The relationship between 'action' and 'url' parameters is not explained, nor are the effects of 'wait' or 'contextId'.

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 a single sentence that front-loads the main purpose. It covers the primary actions without extraneous detail, achieving maximum conciseness while still conveying the essential function.

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 has 4 parameters, no annotations, no output schema, and numerous sibling tools, the description is too brief. It lacks explanation of parameter interactions (e.g., when 'url' is required), contextId usage for multi-page environments, and behavior of the 'wait' parameter. This leaves the agent with significant gaps in understanding.

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 4 parameters with 0% description coverage. The description only mentions 'URL' and the action enum values (reload, back, forward), but fails to explain the meaning of 'contextId', the valid combinations of 'action' and 'url', or the 'wait' options. This imposes a heavy burden on the description for parameter clarity, which it does not meet.

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 tool navigates the current context to a URL or performs reload/back/forward actions. It identifies the resource ('current context') and the actions, providing a clear purpose. However, it does not explicitly differentiate from sibling tools like 'new_page' or 'select_page', which handle pages differently.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, such as requiring a valid page context, or when to use navigation actions versus other tools like 'new_page' for creating new tabs.

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