Disconnect an account from your TikTok app

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

Annotations already mark this destructive and not read-only. The description adds useful non-obvious behavior: the refresh token stops working immediately and restoration requires re-running `tiktok-mcp auth`. That goes beyond the annotation hints, though it does not detail the exact response or further side effects.

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 carry the essential action and consequence with no filler. The destructive effect is front-loaded, and the recovery command is a useful close.

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 core effect and recovery path are covered, and the annotation hints supply the destructive safety signal. However, with no output schema, the agent is not told what a successful revocation returns, and the misleading confirm description leaves a required confirmation ambiguous. A short note on expected response or error conditions would complete it.

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 account parameter is well documented (named account, default to first, call list_accounts). However, the confirm parameter's description appears copied from a deletion/post tool: it talks about a TikTok post being public and deletion not removing it from feeds, which does not explain what 'confirm' means for revoking access. With 100% schema coverage this misleading text is worse than no description at all, and the tool description does not compensate.

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 and resource: it 'hands the token back to TikTok' and 'removes your app from the account's connected-apps list.' This clearly distinguishes revoke_access from sibling tools like list_accounts, get_profile, or post_video.

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 makes the context clear: it is used to disconnect an account and immediately invalidates the refresh token, and it tells the agent how access can be restored by re-running `tiktok-mcp auth`. It does not explicitly name alternatives or when-not conditions, so it stops short of full guidance.

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