douyin_news

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description mentions 'real-time data' which implies freshness and potential rate limits, but doesn't specify update frequency, authentication requirements, data format, or whether this is a read-only operation. For a tool with zero annotation coverage, this leaves significant behavioral gaps.

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 extremely concise at just two Chinese characters and an English translation ('实时数据/抖音热榜'). Every element earns its place by specifying both the temporal aspect ('real-time') and the specific resource ('Douyin hot list'). No wasted words or unnecessary elaboration.

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 lack of annotations, no output schema, and the tool's apparent purpose of providing trending data from a major platform, the description is incomplete. It doesn't specify what data is returned (e.g., list format, fields included), how current the data is, or any limitations. For a news/trending tool in a crowded sibling space, more context would be helpful.

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 tool has 0 parameters with 100% schema description coverage. The description appropriately doesn't discuss parameters since none exist. The baseline for 0 parameters is 4, as there's no need to compensate for missing parameter documentation.

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 '实时数据/抖音热榜' translates to 'real-time data/Douyin hot list', which indicates the tool provides real-time trending content from Douyin (the Chinese version of TikTok). This is a clear purpose statement with a specific resource (Douyin hot list), but it doesn't explicitly state the action verb (e.g., 'fetch', 'retrieve', 'get') or distinguish it from sibling tools that also provide news/trending content from other platforms.

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 guidance on when to use this tool versus alternatives. With 16 sibling tools that appear to provide similar news/trending content from different platforms (e.g., weibo_news, zhihu_news), there's no indication of when Douyin-specific data is needed versus data from other Chinese social media platforms. No exclusions or prerequisites are mentioned.

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