client_user_boot

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

No annotations exist. The description adds minimal behavioral insight beyond naming the operation and labeling it as 'undocumented'. It fails to disclose side effects, required permissions, or whether the tool is destructive or read-only.

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 one sentence, front-loads the core action, and provides a useful qualifier in parentheses. Every word is essential; no filler.

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?

Despite having no parameters and an output schema, the description omits what 'boot' entails, the expected response format, and any risks or termination behavior. The 'undocumented' note hints at instability but does not complete the contextual picture.

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?

With zero parameters, baseline is 4, but the description implies user specificity without explaining how the user is identified (likely via authentication). This ambiguity causes a deduction; the description should clarify that it operates on the authenticated user or requires some implicit context.

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 action: 'Boot the Slack client for a specific user'. It distinguishes itself from the sibling 'client_boot' by specifying user-level targeting and noting the endpoint is undocumented.

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 explicit guidance on when to use this tool versus alternatives like 'client_boot' or other session-related tools. It does not mention prerequisites, when-not-to-use, or contextual preferences.

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