TikTok comments

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

With no annotations, the description carries the full transparency burden. It mentions 'structured data' but does not disclose what fields are returned, whether pagination exists, or any limitations. This lack of detail about return format or behavior is a significant gap for a data-fetching tool.

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, extremely concise and without wasted words. It is appropriately sized for a simple one-parameter tool, though it borders on under-specification.

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?

The tool has no output schema, yet the description does not explain what 'structured' data includes—such as comment text, author, likes, or pagination. This leaves agents uncertain about the return value, making the description incomplete for effective decision-making.

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 schema already describes the only parameter 'url' as 'TikTok video URL', and the description adds no additional meaning beyond 'for a video'. Since schema description coverage is 100%, the baseline of 3 applies without extra contribution from the description.

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 'Structured TikTok comment data for a video' clearly indicates the tool returns comment data for a TikTok video, using a specific resource and scope. It distinguishes itself from siblings like web_data_tiktok_posts and web_data_tiktok_profiles, though it lacks an explicit verb like 'retrieve'.

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 only states what the tool does, with no mention of conditions, exclusions, or comparative 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.