get_smzdm_rank

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

No annotations are present, and the description does not disclose any behavioral traits such as read-only nature, authentication needs, rate limits, or side effects. It only describes the content scope.

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 a single sentence that is somewhat wordy, listing several content types. It is front-loaded with the action, but the length could be reduced without losing clarity.

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?

The tool has a simple parameter and no output schema, yet the description does not mention what the returned data looks like (e.g., a list of items, structure). This omission limits the agent's ability to understand the 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 input schema provides descriptive labels for each enum value of the 'unit' parameter (今日热门, 周热门, 月热门). The description adds no additional semantic information beyond that, and the schema coverage is effectively complete, so a baseline score of 3 is appropriate.

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?

The description clearly states that it gets '热门' (hot/popular) content from 什么值得买 (SMZDM) and lists the types of content included, such as product recommendations and shopping guides. This distinguishes it from sibling tools which target other sources like 36kr or BBC.

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?

No guidance is provided on when to use this tool versus alternatives like get_zhihu_trending or get_weibo_trending. The description does not discuss context or exclusions.

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