get_tiktok_user_followings

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

No annotations provided, so the description carries the full burden. It discloses pagination behavior and required parameters (sec_user_id from get_tiktok_profile). It does not mention rate limits or authentication, but for a straightforward read operation, this is acceptable and no contradictions exist.

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 with zero waste: first sentence states purpose and output structure, second provides pagination guidance. Every word earns its place.

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?

No output schema exists, so the description must explain return values. It lists the fields per entry and describes the pagination termination condition (has_more false). For a list tool, this is complete and actionable.

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%, and the description adds significant context beyond the schema: it explains that page_token and min_time must be passed together from previous response, and that sec_user_id comes from get_tiktok_profile. This helps the agent use parameters correctly.

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 verb 'Get', the resource 'list of accounts a TikTok user follows', and specifies the output format 'as JSON'. It also lists the fields included, distinguishing it from siblings like get_tiktok_user_followers which returns followers in the opposite direction.

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 explicit pagination instructions: 'Pass both page_token and min_time from previous response for pagination; stop when data.has_more is false.' It does not explicitly state when not to use or compare to alternatives, but the pagination guidance is clear and sufficient for correct usage.

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