zhihu_hot_list

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

With no annotations provided, the description carries the full burden. It discloses the authentication requirement (no login) and the return format, which is helpful. However, it does not mention potential rate limits, error behavior, or that this is a read-only operation, though the latter is implied by the verb '获取'.

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, with a front-loaded purpose and a compact return format example. Every sentence adds value, and there is no filler or redundancy.

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 simple parameterless tool with an output schema, the description covers the core purpose, auth requirement, and return shape. It does not include data freshness details or examples, but these are not critical for a hot list retrieval tool, so it is reasonably complete.

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 zero parameters, and the schema already covers everything (100% coverage). Per the rubric, 0 parameters warrants a baseline score of 4; the description correctly does not need to elaborate on parameters.

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 '获取知乎实时热榜' (Get Zhihu real-time hot list) clearly states a specific verb and resource, and the Zhihu platform distinguishes it from sibling hot list tools like weibo_hot_list and douyin_hot_list.

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 implies use for retrieving the current Zhihu hot list and notes '无需登录' (no login required), which is useful context. However, it does not explicitly mention when to use this tool over alternatives like zhihu_search or other hot lists, making the usage guidance only implied.

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