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

Annotations already declare readOnlyHint, openWorldHint and destructiveHint=false, so the description's added value is in disclosing the cost model and the warning that repeated requests may purchase data again — genuinely useful operational context absent from the annotations. It is docked because the pricing statement is internally inconsistent ('at least 10 Nexscope credits' versus '1 credit per request'), which could mislead cost budgeting.

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 first three sentences are front-loaded and efficient — purpose, return shape, pagination. The trailing block of vendor pricing boilerplate is repetitive, partly redundant, and contradicts the earlier credit figure, diluting an otherwise tight definition.

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 does the necessary work of enumerating returned fields (followings array with nickname, unique_id, uid, follower/following counts, signature, avatars) plus total. Missing details are minor: handle formatting conventions and whether cost is incurred on empty results.

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 description coverage is 100%, so handle, trim and min_time are already documented in the schema, and the description's pagination note largely restates min_time's own description. The optional 'trim' flag is never explained in the description, so no meaningful semantics are added beyond the schema.

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 gives a specific verb and resource ('Retrieves the following list') and then disambiguates direction with 'accounts that a TikTok user follows', which cleanly separates it from the sibling social_tiktok_user_followers and social_tiktok_user_following confusion. An agent can select it without opening the schema.

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?

It implies the lookup context ('by their handle') and gives a concrete pagination rule using min_time from the previous response, but it never states when to prefer this over social_tiktok_user_followers, social_tiktok_search_users, or profile tools, and gives no exclusions or prerequisites.

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