get_tiktok_profile

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

No annotations are provided, so the description carries full burden. It mentions cost (2 credits) and lists returned fields, but does not disclose authentication requirements, rate limits, or behavior on missing profiles. This is a moderate gap given no annotation support.

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 concise, front-loaded sentences with no fluff. Every sentence adds value: purpose, returned fields, alternative tool, and cost.

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 and no annotations, the description sufficiently lists returned fields and provides cost. It lacks error handling or null field behavior, but overall is fairly complete for a straightforward profile 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?

Schema provides 100% coverage for the single parameter (uniqueId) with a clear description. The tool description adds no additional param info beyond schema, so baseline 3 is appropriate.

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 retrieves a TikTok creator's profile and lists specific fields (display name, follower count, etc.). It distinguishes from sibling tool list_tiktok_niches by noting that tool is for browsing niche taxonomy.

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 context on when to use this tool vs alternatives: directs to list_tiktok_niches for browsing niche taxonomy. It also mentions cost (2 credits). However, it does not explicitly state when NOT to use this tool or cover other sibling tools.

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