ws_unsubscribe_all

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

No annotations are provided, so the description must disclose behavioral traits. It only states the action (unsubscribe from all) without explaining whether it's destructive, reversible, affects the current connection only, or requires re-subscription. The description lacks transparency about the scope and consequences of the operation.

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, concise sentence that directly states the tool's action. There is no filler or redundant information. It is well-structured and easy to parse.

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 tool has no parameters and no output schema, the description should explain the full behavior. It states the primary effect but omits important details like return value, idempotency, and whether it applies to the current session or globally. It is minimally adequate but leaves several practical questions unanswered.

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 tool has zero parameters, and the schema coverage is 100% with an empty properties object. The baseline for 0 parameters is 4, and the description doesn't need to add parameter details since there are none. This is appropriate.

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 tool's purpose: 'Unsubscribe from all active subscriptions'. It uses a specific verb and resource, and the 'all' scope distinguishes it from the sibling tool ws_unsubscribe, which presumably handles individual subscriptions. The purpose is unambiguous and immediately understandable.

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 like ws_unsubscribe or ws_list_subscriptions. It doesn't mention prerequisites, side effects on the current websocket connection, or whether it's irreversible. There is no explicit exclusion or context beyond the literal action.

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