tiktok_profile_audience_getGet audience location demographics for a TikTok profile by handle.
| Name | Required | Description | Default |
|---|---|---|---|
| handle | Yes | TikTok handle to look up, with or without a leading @. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint and openWorldHint, so the safety profile is known. However, the description adds no extra behavioral context such as data freshness, rate limits, whether a public profile is required, or what exactly is included in 'location demographics'. It merely restates the resource, offering no insights beyond 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 description is a single, concise sentence that is fully front-loaded with the core purpose. There is no fluff or redundant wording, making it efficient for an agent to parse quickly.
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 and only a minimal description, the agent is left without any indication of the response structure (e.g., a breakdown of locations, percentages). The tool is simple (one parameter) but the lack of output details and the presence of a near-twin sibling (tiktok_profile_region_get) make it inadequately complete for confident selection and invocation. More context about what 'demographics' entails would be necessary.
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% and the schema thoroughly describes the handle parameter (including format, length constraints, and whether @ is allowed). The description adds no additional meaning about the parameter, so the baseline of 3 is appropriate; it does not need to repeat schema details but also does not contribute anything new.
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 'Get audience location demographics for a TikTok profile by handle' clearly identifies the action (get) and resource (audience location demographics) and includes the lookup method (by handle). It is specific enough to distinguish from general profile tools like tiktok_profile_get, though it does not explicitly differentiate from the similar-sounding tiktok_profile_region_get, leaving some ambiguity about what 'demographics' adds over 'region'.
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 no guidance on when to use this tool versus its many siblings. There is no mention of alternatives, exclusion conditions, or context such as 'use this when you need geographic distribution of followers'. Given the large sibling set (e.g., tiktok_profile_engagement_get, tiktok_profile_region_get, tiktok_profile_followers_list), this absence makes it hard for an agent to know if this is the right tool.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
Each tool is clearly scoped to a specific platform and action (e.g., facebook_post_get vs instagram_post_get). Descriptions explicitly differentiate similar tools across platforms, and within-a-platform tools like tiktok_search_videos_list vs tiktok_search_hashtag_list have clear disambiguation notes.
All 167 tools follow a strict `platform_resource_action` pattern (e.g., youtube_video_comments_list). No mixing of styles—snake_case throughout, with consistent verb ordering (get, list, search, etc.).
The server has 167 tools, which is far beyond the typical well-scoped range of 3-15. While the broad multi-platform scope justifies many tools, this extreme number makes the tool surface overwhelming and difficult for an agent to navigate efficiently.
The tool set covers a wide range of platforms and operations including profile retrieval, post/video fetching, comments, search, transcripts, and ad library access. Minor gaps exist (e.g., no Facebook events or LinkedIn messaging), but the surface is comprehensive for a read-only data aggregation use case.