实时数据/36氪热榜

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, the description offers no information about what the tool does (e.g., whether it retrieves, updates, or monitors data), its operational characteristics (e.g., rate limits, authentication needs), or expected outcomes. This leaves the agent completely in the dark about the tool's behavior.

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 brief ('实时数据/36氪热榜'), this is not true conciseness but rather under-specification. It fails to convey essential information about the tool's function and usage, making it inefficient rather than succinct. The structure doesn't front-load critical details, as it provides no actionable content.

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 lack of annotations and output schema, the description is severely incomplete. It doesn't explain what the tool returns (e.g., a list of trending topics from 36Kr), how it behaves, or when to use it. For a tool in a family of similar '热榜' tools, this minimal description fails to provide the necessary context for effective agent use.

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, meaning the schema fully documents the lack of inputs. The description doesn't add any parameter information, which is appropriate since there are no parameters to explain. This meets the baseline expectation for a parameterless 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 no guidance on when to use this tool versus alternatives. It doesn't mention any specific context, prerequisites, or differences from sibling tools like '实时数据/微博热搜' or '实时数据/知乎热榜'. Without any usage instructions, the agent has no basis for selecting this tool over others in the same category.

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