get_douyin_hot_list

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

No annotations are provided, so the description carries the full burden. It does not say whether this hits an external service, how fresh the data is, whether results are ranked or paginated, or what the response looks like. Only the general domain (hot topics) is conveyed.

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?

A single short sentence with the resource front-loaded and no filler. It is efficient, though extremely terse, leaving little room to convey behavioral detail.

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?

With no parameters and no output schema, the description only needs to convey the return's nature, which it does vaguely ('hot list'). It does not indicate what fields come back (ranks, heat scores, links) or how current the data is, leaving a gap for an agent deciding whether results suffice.

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 takes zero parameters, so the schema has nothing to document and the baseline is 4. The description correctly implies no inputs are needed.

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 names a specific resource (抖音热点榜 / Douyin hot search list) and implies a read of that list. It is clear on what it fetches, but does not explicitly contrast itself with the sibling get_hot_words, which covers a similar topical area.

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?

'配合站内热词做选题参考' implies the use case (topic selection, used together with in-site hot words), which hints at a relationship with get_hot_words. However, it never states when to call this tool versus that sibling, nor any preconditions.

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