实时数据/知乎热榜

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. However, it offers no information about what the tool does behaviorally—whether it fetches data, requires authentication, has rate limits, returns real-time or cached data, or any other operational traits. This leaves the agent with no understanding of how the tool behaves beyond its name.

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 but under-specified, not efficiently informative. It consists of a single phrase that mirrors the tool name, failing to convey any meaningful information. While brevity is present, it doesn't earn its place by adding value, making it more of a placeholder than a helpful description.

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 complexity implied by '实时数据' (real-time data) and the lack of annotations or output schema, the description is completely inadequate. It doesn't explain what the tool returns, how to interpret results, or any operational context. For a tool presumably fetching trending data from Zhihu, this leaves critical gaps in understanding its functionality and output.

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, and the schema description coverage is 100%, meaning there are no parameters to document. The description doesn't need to compensate for any parameter gaps. A baseline score of 4 is appropriate as the absence of parameters is inherently clear, though not a perfect 5 since the description could theoretically mention this explicitly.

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?

Tautological: description restates name/title.

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. It doesn't mention any specific context, prerequisites, or exclusions. With multiple sibling tools for different platforms (e.g., 微博热搜, 抖音热榜), there's no indication of why one would choose this tool over others, making it misleadingly generic for a platform-specific tool.

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