wavexis_navigate

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

Discloses side effects (network request, replaces page content) and auto-creation of session if session_id is omitted. This adds value beyond annotations (readOnlyHint=false, destructiveHint=false) and is consistent with them.

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 sentences front-loaded with main action, usage guidelines, and side effects. No wasted words, clearly 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?

Covers main purpose, usage guidelines, side effects, and return value (status, url). Missing details on wait strategy options, but schema descriptions (if present) would fill the gap. Output schema exists and is referenced.

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?

With schema description coverage at 0%, the description should compensate but only mentions 'configurable wait strategy' without detailing parameters or explaining their meanings. The schema itself has descriptions, but per context coverage is 0%.

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 uses specific verb 'navigate' and resource 'browser to a URL', clearly distinguishing from sibling tools like wavexis_back/wavexis_forward (history navigation) and wavexis_act (natural-language interaction).

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 (direct URL navigation) and when to use alternatives (history or NL), providing clear context for tool selection.

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