实时数据/知乎热榜

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

With no annotations provided, the description carries the full burden of behavioral disclosure but offers none. It doesn't indicate whether this is a read operation, mutation, or other behavior; doesn't mention rate limits, authentication needs, or data format; and provides no insight into what '热榜' (hot list) entails (e.g., ranking criteria, update frequency). This leaves the agent completely in the dark about how the tool behaves.

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?

While technically concise (just the tool name repeated), this is under-specification rather than effective brevity. The description fails to front-load critical information and doesn't use its limited space to add any value beyond what's already in the name. Every sentence should earn its place, but here there's essentially no meaningful content to evaluate.

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 '热榜' (hot list data) and the complete lack of annotations and output schema, the description is severely incomplete. It doesn't explain what data is returned, in what format, or with what limitations. For a data-fetching tool with no structured metadata, this description provides almost no useful context for an AI agent to understand or use the tool effectively.

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 (empty schema). Since there are no parameters to document, the description doesn't need to compensate for any gaps. The baseline for 0 parameters is 4, as the description appropriately doesn't waste space discussing non-existent 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?

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 absolutely no guidance on when to use this tool versus its many siblings (e.g., 实时数据/微博热搜, 实时数据/抖音热榜). There's no indication of context, prerequisites, or alternatives. The agent must guess based solely on the platform name (知乎) without any usage instructions.

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