net_ws

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

With no annotations, the description carries the behavioral disclosure burden. 'List' implies a read-only operation and the returned data (frame counts, recent frames) is stated, but the description is silent on whether sessionId scopes results, whether all sessions are included by default, or any limits on how many frames are returned.

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 sentence with the action and resource front-loaded. It contains no filler or redundant restatement of the tool name.

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?

The tool has no output schema and no annotations, so the description is the only source of behavior. Yet it omits the meaning of the single sessionId parameter and any default-scope details. For a tool with a generic sibling like net_list, this is insufficient for confident, 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?

The only parameter, sessionId, is completely undocumented in the schema (0% coverage) and is not mentioned in the description. The description adds no meaning to this parameter, leaving an agent unable to determine whether it filters by browser session, is required, or what format it expects.

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 a specific verb ('List') and a clear resource ('WebSocket connections'), with result contents summarized as frame counts and recent frames. It differentiates from generic network siblings like net_list by naming WebSockets explicitly, though it doesn't directly contrast itself with sibling tools.

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?

No when-to-use guidance is provided. The description does not say when to choose net_ws over net_list, net_get, or other network tools, and it gives no exclusions, prerequisites, or context. The only implied usage is from the tool name and content summary.

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