tiktok_get_user_analytics

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

With no annotations provided, the description carries the full burden. It states 'without downloading files' implying a read-only operation and lists the metrics returned. However, it omits details on authentication requirements, rate limits, data recency bounds, and whether the analysis is computed on-the-fly or cached. This is adequate but not thorough.

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, front-loaded sentence that immediately states the verb and resource. It is 20 words with no filler, and every term ('analyze', 'engagement metrics', 'without downloading') adds value. Ideal conciseness.

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 should explain the return structure. It mentions 'top performing posts' but does not specify whether those are full post objects, IDs, or thumbnails. It also fails to describe the format of engagement metrics (e.g., per-post breakdown vs. aggregate). A user cannot fully anticipate the tool's output.

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?

The input schema has 100% coverage for both parameters (username and max), so the baseline is 3. The description does not add any extra meaning beyond the schema descriptions; it does not clarify how 'max' affects the analysis output or what formats are accepted for username.

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 uses the explicit verb 'Analyze' targeting 'a TikTok profile's recent engagement metrics', listing specific outputs like views, likes, comments, shares, engagement rate, and top performing posts. It clearly differentiates from sibling tools, which focus on extraction or downloading, by emphasizing 'without downloading files'.

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 no explicit guidance on when to use this tool versus alternatives like tiktok_get_user_posts or tiktok_extract_post. While it hints at not needing downloads, it does not explain trade-offs (e.g., aggregated vs. raw data) or scenarios where this tool is preferred.

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