get_tiktok_user

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

With no annotations, the description carries full burden. It only states the action (get) but does not disclose behavioral traits such as rate limits, authentication failure behavior, pagination, or response structure. The mention of return fields is helpful but insufficient for transparency.

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 a single sentence, making it very concise. It front-loads the core purpose. However, it could benefit from a slight restructuring to include key behavioral points without adding length.

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 the simplicity (1 param, no output schema), the description provides a basic idea of return values but is not exhaustive. It lacks details on errors, authentication requirements, and rate limits. It is minimally viable but could be more complete.

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% (access_token documented), so baseline is 3. The description adds no further meaning to the parameter beyond what the schema provides. It does not explain how the token is used or alternative ways to provide it.

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 verb 'Get', the resource 'authenticated TikTok user profile', and enumerates sample return fields (follower count, video count). This distinguishes it from sibling tools like get_tiktok_video and list_tiktok_videos, which focus on videos.

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 guidance is provided on when to use this tool versus alternatives, nor are prerequisites like needing an access_token mentioned. The description does not address when not to use it or suggest other tools for related tasks.

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