TikTok MCP

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions the input type ('TikTok video url') and lists return details, but it lacks information on potential errors, rate limits, authentication needs, or whether the operation is read-only or has side effects. This leaves significant gaps in understanding the tool's behavior.

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 moderately concise with three sentences, but it includes redundant phrasing ('This is used for getting the details of a TikTok post') that doesn't add value. The information is front-loaded with the purpose, but the structure could be improved by eliminating repetition and tightening the language.

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 lack of annotations and output schema, the description is incomplete for a tool that returns multiple metadata fields. It lists return details but doesn't specify the format, data types, or potential null values, leaving the agent uncertain about the output structure. For a tool with no structured output support, more detail is needed.

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 input schema has 100% description coverage, so the schema already documents the single parameter 'tiktok_url' with examples. The description adds minimal value by repeating 'Supports TikTok video url as input' without providing additional syntax or format details beyond the schema, meeting the baseline for high schema coverage.

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 with a specific verb ('Get') and resource ('details of a TikTok post'), and it distinguishes the scope by mentioning it returns various metadata fields. However, it doesn't explicitly differentiate from sibling tools like tiktok_available_subtitles or tiktok_get_subtitle, which focus on subtitles rather than general post details.

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, such as the sibling tools for subtitles. It states 'This is used for getting the details of a TikTok post,' which is tautological and offers no context on exclusions or prerequisites, leaving the agent without usage direction.

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