wavexis_session_open

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

Discloses side effects: launches browser process, allocates server-side state, may open network connections. This adds value beyond annotations (openWorldHint, destructiveHint) and matches them. No contradiction.

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?

Description is concise with one sentence each for purpose, usage, side effects, and return. Every sentence is informative and front-loaded with the main purpose.

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 complexity (14 parameters, many siblings, annotations, no output schema but described), the description covers purpose, usage, side effects, and return format adequately. The parameter details are in the schema, so 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?

The tool description does not describe any of the 14 parameters; schema descriptions are present but the context signal shows 0% schema_description_coverage in the description. With low coverage, the description should compensate, but it does not. Only a basic mention of the return structure is provided.

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 launches a persistent browser session, using the verb 'Launch' and the resource 'browser session'. It distinguishes from sibling `wavexis_navigate` by specifying that `wavexis_navigate` with session_id omitted is for one-off fetches.

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 instructs to call once at task start and reuse the session_id, and contrasts with `wavexis_navigate` for one-off page fetches. Provides 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.