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

Goes well beyond the readOnly/openWorld annotations by disclosing the return shape (user and stats objects), credit cost, and the cache-vs-live-scrape tradeoff with cache_max_age. However, the pasted pricing fragments conflict with each other ("at least 10 Nexscope credits" vs "1 credit per request"), which leaves the actual cost ambiguous.

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 opening two sentences are well-structured, but they are followed by raw API-doc artifacts ("TikTok Profile API View Pricing...") and a cache paragraph that duplicates the schema verbatim, including a markdown link. The conflicting credit figures further hurt readability rather than adding information.

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?

Return-value structure, cost and caching are all covered, which is good given there is no output schema. The significant gap is that the schema has zero required parameters and the description never says at least one of handle or user_id must be supplied, nor what happens on failure.

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, user_id and the cache_max_age enum are already fully documented, including the caching semantics. The description only restates "by their handle or user_id" and the cache behavior, adding no syntax or format detail 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?

States a specific verb and resource ("Fetches public profile data for a TikTok user by their handle or user_id") and enumerates the fields returned. It also carves out scope against the video/follower siblings ("only returns profile metadata, not the user's actual videos or followers list"), though it does not address near-neighbours like social_tiktok_profile_region or social_tiktok_profile_videos by name.

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?

Gives a clear positive use case ("looking up a creator's identity, bio, and account stats") plus an explicit exclusion that routes the agent to video-list and follower-list tools instead. It stops short of naming those alternatives or stating prerequisites such as needing at least one identifier.

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