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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful behavior beyond that: a concrete 26-credit cost, a floor of at least 10 credits, and the warning that repeated requests may purchase the data again. It stops short of describing rate limits or error/exception behavior.

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 same content is duplicated almost verbatim three times, and the 26-credit cost is restated at least four times plus a stray "API View Pricing" boilerplate fragment. The informative opening sentence is buried under repetition, so sizing and front-loading both suffer badly.

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?

There is no output schema, but the description compensates by naming the returned `audienceLocations` array and its fields (`country`, `countryCode`, `count`, `percentage`). Combined with the cost disclosure, an agent has enough to call it and interpret the result; only exception and failure behavior is left undefined.

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% with a single required parameter, so the schema already carries the burden of documenting `handle`. The description adds nothing about handle format (with or without the @ symbol) or normalization, so this sits at the baseline.

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: it retrieves audience demographic data for a TikTok user, specifically follower locations by country. The scope limitation ("Right now you can only get the audience countries") meaningfully separates it from siblings like social_tiktok_user_followers and social_tiktok_user_following, though no sibling is named explicitly.

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 implied rather than stated: an agent can infer it should call this when it needs geographic breakdown of a TikTok user's followers, and the note that only country data is available sets an expectation boundary. There is no explicit when-to-use versus alternatives guidance and no stated prerequisites beyond the handle.

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