get_tiktok_user_followers

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

No annotations present; description covers pagination behavior and return fields but does not explicitly state that the operation is read-only or mention authentication requirements.

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, front-loaded with purpose, no redundancy, every sentence adds value.

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?

Lists follower fields but does not describe overall response structure beyond mentioning data.has_more; adequate for a simple list retrieval tool.

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 covers all parameters; description adds context beyond schema by linking sec_user_id to get_tiktok_profile and explaining pagination token usage.

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?

Clearly states the tool retrieves a TikTok user's follower list as JSON and lists the fields included, distinguishing it from siblings like get_tiktok_user_followings.

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?

Provides explicit pagination instructions (page_token and min_time) and a stopping condition, but does not contrast with siblings or specify when to choose followers over followings.

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