tiktok_challenge_list

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

No annotations are provided, so the description carries full burden. It mentions cursor-based pagination but does not disclose other behavioral traits such as authentication needs, rate limits, or error handling. The description is somewhat transparent but incomplete for a tool with no annotation safety net.

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 concise: two sentences that clearly state the purpose and key feature (cursor-based pagination). Every sentence earns its place; 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?

Given the complexity (simple list tool with two parameters and no output schema) and presence of sibling tools like tiktok_challenge and tiktok_search_hashtag, the description covers the essential functionality and pagination. However, it could be more complete by hinting at the response structure (e.g., what fields are returned in each video). Still, it is adequate for selection and basic invocation.

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 coverage is 100%, so parameters have descriptions. The description adds value by clarifying that the 'id' parameter is a 'Hashtag id returned by the hashtag detail endpoint', which provides context for obtaining the id. The cursor parameter is briefly described. This extra context justifies a 4 rather than baseline 3.

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 it retrieves TikTok hashtag posts for a given hashtag id with cursor-based pagination. It uses specific verb 'Retrieve' and resource 'TikTok hashtag posts', distinguishing it from sibling tools like tiktok_challenge (hashtag details) and tiktok_search_hashtag (hashtag search).

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 implicitly indicates use when you have a hashtag id and want videos, but it does not explicitly state when to use this tool versus alternatives, nor does it mention prerequisites or exclusions. While the sibling list provides context, the description itself lacks explicit usage guidance.

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