实时数据/抖音热榜

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 fails to describe any behavioral traits such as whether this is a read-only operation, potential rate limits, authentication requirements, or what the tool returns (e.g., a list of trending topics). The description is essentially empty in terms of behavioral context, making it impossible for an agent to understand 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 the description is extremely concise (a single phrase), this brevity results in under-specification rather than effective conciseness. It does not front-load critical information or provide any structured details about the tool's functionality. The description fails to earn its place by adding value, making it inefficient despite its short length.

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 tool's complexity (implied by being part of a '实时数据' or 'real-time data' family with many siblings) and the lack of annotations and output schema, the description is completely inadequate. It does not explain what the tool returns, how it interacts with the system, or any contextual nuances, leaving significant gaps for an agent to understand and 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, and the schema description coverage is 100% (since there are no parameters to describe). In such cases, the baseline score is 4, as there is no need for the description to compensate for missing parameter information. The description does not add any parameter semantics, but this is acceptable given the absence of 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 offers no guidance on when to use this tool versus alternatives. It does not mention any specific context, prerequisites, or exclusions, nor does it reference sibling tools (e.g., '抖音热榜' vs. '微博热搜') to help differentiate usage scenarios. This leaves the agent with no information to make an informed selection among similar tools.

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