game_websocket

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

No annotations are provided, so the description carries the full behavioral burden. It lists actions but does not disclose the stateful lifecycle of the connection, connection failure handling, message framing expectations, or what the 'status' action returns. Connect-before-send is only implied by the action names.

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 very concise and front-loaded with the resource and core operations. However, it omits the 'status' action that appears in the schema, so the brevity sacrifices a small amount of completeness.

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 stateful WebSocket tool with no annotations and no output schema, this description is too thin. It does not cover connection lifecycle, error handling, return values, or when to prefer this over related networking tools. The schema covers parameter names but not the behavioral context needed for correct 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%, and each parameter has a clear inline description, meeting the baseline for parameter semantics. The tool description itself does not add parameter-level value such as URL format requirements, message payload expectations, or action-specific constraints.

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?

Description clearly identifies the resource (WebSocket) and the operations (connect/disconnect/send messages), which maps well to the schema's action values. It does not explicitly differentiate itself from siblings like game_http_request or game_multiplayer, but the WebSocket focus is distinct enough for basic clarity.

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?

There is no guidance on when to use this tool versus alternatives such as game_http_request or game_multiplayer. The description also does not mention prerequisites like requiring a connection before sending messages or when to use the 'status' action.

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