connect_websocket

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

No annotations are provided, so the description bears full responsibility. It only states it connects and prepares, but omits behavioral traits like connection timeout, idempotency, error conditions, or what happens if called again.

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?

Extremely concise: two short sentences front-loading purpose and usage order. No redundant words.

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?

For a simple connection tool with no parameters or output schema, the description covers essential usage (call first) and purpose. However, it doesn't explain what the tool returns or how to confirm successful connection, which an agent would need.

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?

Tool has zero parameters, so the description adds no parameter-level info beyond the schema. Baseline 4 is appropriate as there's nothing to clarify.

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 action (connect WebSocket), target (neko), and purpose (prepare for mouse/keyboard events). It distinguishes itself from sibling tools, which are all action-oriented, by being the only setup/connection tool.

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 says 'Nên gọi đầu tiên' (Should call first), giving clear when-to-use guidance. No alternatives are mentioned, but as the only connection tool, this is sufficient. Could add when not to call.

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