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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, but the description goes further by documenting the returned shape, the pagination mechanism via min_time, and a credit/cost model with a warning that repeated requests may purchase data again. The pricing block is internally muddled ('at least 10 Nexscope credits' versus '1 credit per request'), which blunts the otherwise valuable cost disclosure, but it does not contradict the annotations.

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 core sentences are front-loaded and efficient, but the trailing pricing block ('TikTok Followers API View Pricing Scrapes followers of a TikTok account 1 credit per request / Actual supplier units are reported per request. Examples are not guaranteed prices.') reads like unfiltered vendor boilerplate and repeats or undercuts the earlier cost sentence.

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?

With no output schema, the description usefully compensates by naming the follower object fields and the total counter, and it covers pagination. However, for a tool where required is empty and all four parameters are optional, it never states that a handle or user_id must be supplied, leaving a real risk of an empty-argument call.

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 every parameter is already documented in the schema (including user_id's faster response times). The description only restates that lookup can be done 'by handle or user_id' and adds the pagination loop instruction for min_time; it says nothing about trim or about the fact that all parameters are optional yet at least one identifier is practically needed.

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 states a specific verb and resource ('Retrieves the follower list of a TikTok account') and names both lookup keys (handle or user_id). It implicitly separates itself from the sibling social_tiktok_user_following by consistently saying 'followers', but it never names that sibling explicitly, so an agent must infer the direction of the relationship.

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?

Usage is conveyed only through the phrase 'useful for seeing who follows a creator or getting subscriber data', which is illustrative rather than directive. There is no explicit guidance on when to prefer this over social_tiktok_user_following, social_tiktok_user_audience, or social_tiktok_profile, and no cost-avoidance advice despite the credit warnings.

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