connect-browser-with-ws

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action but doesn't explain what 'connect' means—whether it establishes a new session, reconnects an existing one, requires authentication, has side effects, or what happens on failure. This leaves critical operational traits undefined for the agent.

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, efficient sentence that directly states the tool's function. It's front-loaded with the core action and includes a helpful note about parameter sourcing, though it could be slightly more informative without sacrificing brevity.

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 of a browser connection tool with no annotations and no output schema, the description is insufficient. It doesn't cover what the tool returns, error conditions, or how it integrates with sibling tools, leaving the agent with incomplete context for reliable invocation.

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 the schema fully documents the three parameters. The description adds minimal value by referencing the wsUrl source from 'open-browser', which provides some context but doesn't elaborate on parameter interactions or usage beyond what's in the schema descriptions.

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 states the tool's purpose as connecting a browser with a WebSocket URL, which is a clear action but lacks specificity about what 'connect' entails operationally. It doesn't distinguish itself from sibling tools like 'open-browser' or 'get-opened-browser', leaving ambiguity about its unique role in the browser management workflow.

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 provides no guidance on when to use this tool versus alternatives. It mentions getting the wsUrl from 'open-browser', implying a sequence, but doesn't clarify if this is a prerequisite or alternative to other tools like 'create-browser' or 'update-browser', leaving the agent to infer usage context.

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