Connect a TikTok account

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

With no annotations, the description carries the full behavioral disclosure burden. It discloses the key non-obvious behavior: the operation produces a QR login link that must be shared with a human, and completion is asynchronous (requires polling tiktok_connect_status). It does not mention error conditions, prerequisites, or permissions, but the core interactive workflow is well explained.

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 two sentences long, immediately states the primary action, and the second sentence explains the follow-up steps. Every sentence provides essential guidance with 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?

Although there is no output schema, the description mentions the key return value (connect_url) and the polling sibling. It covers the essential workflow for a connect operation. It could be more complete by noting failure scenarios or prerequisites, but the core context is sufficient.

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?

Schema description coverage is 80%, so the schema already documents most parameters. The description adds no parameter-specific meaning beyond the schema; it only references the output connect_url. Thus a baseline 3 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 uses a specific verb and resource: 'Create a shareable TikTok QR login link.' This clearly states the tool's purpose and distinguishes it from siblings like tiktok_connect_status (which polls connection status) and tiktok_accounts (which lists accounts).

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 gives clear usage context: generate the link, send connect_url to the human, then poll tiktok_connect_status. It implicitly explains when to use this tool versus the status-polling sibling. It does not explicitly state when not to use it or mention alternative tools, so it misses the top score.

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