get_tiktok_audience

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

Discloses missing data placeholder shape (all 0.0) and interpretation rule (male+female=0 as missing). Mentions credi cost. No annotations provided, so description carries the burden; adequately covers key behavioral traits.

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?

Concise, front-loaded with purpose. Every sentence adds value: purpose, field list, missing data handling, cost. No unnecessary words.

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?

Covers output fields, missing data behavior, and cost. No output schema exists, so description compensates well. Could optionally describe output format more, but sufficient for a simple 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?

Single parameter uniqueId is described in schema with 100% coverage. Description adds example and clarifies no '@' prefix and no URL, providing extra clarity 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?

Clearly states 'Get a TikTok creator's audience demographics' with specific fields listed. Distinguishes from sibling tools like get_instagram_audience via platform prefix.

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?

No explicit guidance on when to use this tool vs. alternatives. Usage is implied through purpose, but no when-to-use or when-not-to-use advice is given.

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