TikTok posts

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

No annotations are present, and the description only lists output metrics without disclosing behaviors such as whether it performs a read-only fetch, any rate limits, or error conditions. It adds minimal transparency about the operation itself.

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 single sentence is front-loaded with key information and contains no unnecessary words. It is appropriately sized for a simple data retrieval tool.

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?

For a tool with one parameter and no output schema, the description provides the essential return value context. It lists the main metrics, which is sufficient for basic invocation, though it does not specify the exact output structure (e.g., object vs array) or provide usage examples.

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 covers 100% of parameters with 'url' described as 'TikTok video URL'. The description does not add further semantic detail about the parameter, so the baseline score of 3 applies.

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 returns structured TikTok video data with specific metrics (views, likes, shares, comments). The verb is implied but the resource and scope are explicit, distinguishing it from sibling tools like web_data_tiktok_profiles and web_data_tiktok_comments.

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. The description does not mention any exclusions or alternative tools, leaving the agent to infer usage solely from the tool name.

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