rba_disconnect_client

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

No annotations are provided, and the description only says 'Close,' which is a destructive action. It does not disclose whether the action is reversible, what side effects it has on the client list, or whether confirmation is required. The description fails to carry the burden of behavioral transparency.

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, focused sentence with no filler, which is appropriate for a simple operation. However, it borders on under-specification, though for this tool, brevity does contribute to clarity.

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?

With no output schema and no annotations, the description is incomplete for an agent. It does not indicate the return value, whether the disconnection is confirmed, or how to identify a specific client. The tool is simple, but the missing context makes it inadequate 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?

The schema has zero description coverage for the parameter clientId, and the tool description does not mention it at all. The agent receives no guidance on how to obtain a valid client ID or that it refers to the ID from rba_clients, leaving the parameter meaning entirely inferred.

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 ('Close') and the specific resource ('one connected RBA websocket client'), which distinguishes it from server-level operations like rba_ws_stop. It is concise and unambiguous.

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 guidance is provided on when to use this tool versus alternatives such as rba_ws_stop or rba_disconnect_client. The description gives no context for selecting this tool over sibling tools or any exclusions.

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