Suspend a Tailscale user to immediately revoke tailnet access and disconnect their devices. Restore access later with the restore action.
Suspend a user, immediately revoking their access to the tailnet. Their devices will be disconnected. Can be reversed with tailscale_restore_user.
| Name | Required | Description | Default |
|---|---|---|---|
| userId | Yes | The user ID to suspend |
Changes observed during successful MCP inspections.
v0.13.3Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Description adds value beyond annotations: specifies that access is revoked immediately and devices are disconnected. Annotations already indicate destructiveHint=true, but description provides concrete behavioral detail. No contradiction.
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?
Two sentences, front-loaded with primary action and effect, followed by relationship to sibling. No wasted words.
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 simple single-parameter suspend tool, description covers key effects and undo path. No missing crucial context.
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?
Only one parameter (userId) with full schema coverage. Description adds no additional info beyond the schema's own description. Baseline score of 3 applies.
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 states the action (suspend a user) and the immediate effect (revoke access, disconnect devices). Explicitly distinguishes from sibling tailscale_restore_user by noting reversibility.
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?
Mentions reversibility with tailscale_restore_user, guiding when to use this tool for temporary suspension. However, lacks explicit context on when not to use (e.g., permanent deletion alternatives) or prerequisites.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.