实时数据/稀土掘金热榜

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-only operation, if it requires authentication, what rate limits might apply, or what format the data returns. The description fails to provide any behavioral context beyond the implied action of accessing a '热榜' (hot list).

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 (a single phrase), this description represents under-specification rather than effective brevity. It doesn't front-load critical information about the tool's function, and the single phrase fails to earn its place by adding meaningful value beyond the tool name. True conciseness balances brevity with completeness, which this lacks.

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 apparent simplicity (0 parameters, no output schema), the description is incomplete. While it identifies the data source ('稀土掘金热榜'), it doesn't explain what the tool actually does (e.g., retrieves current rankings), what format the data comes in, or how it differs from sibling tools. For a tool in a family of similar '热榜' tools, more differentiation and functional clarity is needed.

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, so the schema fully documents the input requirements (none). The description doesn't need to compensate for parameter documentation gaps. While it doesn't add any parameter-specific information (which isn't needed), it appropriately matches the parameterless nature of the tool.

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. Users must infer usage based solely on the tool name, which is insufficient for effective tool selection among similar options.

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