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

With no annotations, the description should disclose behavioral traits like authentication requirements, rate limits, or error handling. It only describes the returned data but omits any behavioral context, such as what happens if the handle is invalid or if the profile is private.

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 two sentences plus a parameter note, all essential and front-loaded. No redundant 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?

Given no output schema, the description lists the key data fields returned (follower/following counts, etc.). For a simple profile endpoint with two parameters, this is sufficient. It could mention response format or pagination, but not critical.

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 coverage is 100%, but the description adds value by clarifying that 'handle' accepts '@username or numeric user_id' and explaining the 'expand' parameter: 'Return the full untrimmed payload. Default false = compact JSON.' This goes beyond the schema descriptions.

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 clearly states the tool fetches a TikTok creator's public profile with specific data points (follower/following counts, total videos, likes, etc.). It distinguishes from sibling tools like tiktok_creator_followers or tiktok_creator_videos by focusing on the overall profile.

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 explicit use cases: 'influencer discovery, creator analytics, and audience-size vetting for UGC/brand deals.' It does not explicitly state when not to use it, but the purpose alone implies it's for profile data, not for followers or videos, which are covered by siblings.

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