navigate

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

No annotations exist, so the description fully covers behavioral traits: element refs become stale after reload, waits for settle, overwrites active tab, and first call auto-redirects to virtual_desk.

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 information-dense in a single paragraph, front-loading the main purpose and covering key warnings. While concise, it could benefit from bullet points for improved readability.

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 actions, side effects, and usage warnings well. Lacks mention of return value (e.g., success/error) since no output schema, but for a navigation tool the behavioral completeness is high.

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 coverage is 100%, but the description adds valuable context: explains the url parameter's role for goto, enumerates and clarifies action enum values with side effects (stale refs on reload), and describes settle_ms as extra wait time.

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 verb 'navigate' and resource 'ACTIVE tab', enumerates specific actions (goto, back, reload) with examples, and implicitly distinguishes from sibling tools like 'switch_tab'.

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 warns about overwriting the active tab, instructs to call virtual_desk first, and notes the auto-redirect on first call, providing clear when-to-use and when-not-to-use guidance.

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