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

No annotations exist, so the description carries the full burden. It does add genuine value beyond structured fields: explicit per-call pricing ($0.01/profile + $0.002/video) and the shape of the result objects. It omits auth/API-key requirements, rate limits, and how the required 'profiles' param interacts with the optional 'hashtags' mode.

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?

Three tight sentences, front-loaded with capability, then usage, then return shape, then cost. Nothing is padding — even the return-type sentence earns its place because there is no output schema.

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 no annotations, the description usefully covers returns, cost, and call context. The main omission is the profiles-vs-hashtags usage relationship, which an agent needs to invoke the tool correctly in hashtag-only scenarios.

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 all three parameters are already documented in the schema; baseline 3 applies. The description adds no param-level meaning, notably failing to clarify the apparent tension between the required 'profiles' field and the hashtag-only trending-videos use case.

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?

States a specific verb (scrape) and resource (TikTok profiles and videos) and enumerates the data returned (follower counts, likes, video metadata and stats). The platform name alone distinguishes it from the instagram_scraper, youtube_scraper, and linkedin_profile_scraper siblings.

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?

"Use when researching influencers, tracking social engagement or analyzing TikTok content" gives clear triggering contexts. However it never states when NOT to use it and never names the sibling scrapers (instagram_scraper, youtube_scraper) as the alternatives for non-TikTok platforms, leaving that inference to the agent.

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