weibo_news

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

No annotations are provided, so the description carries full burden. It mentions '实时数据' (real-time data), hinting at freshness, but doesn't disclose critical behaviors like rate limits, authentication needs, data format, or whether it's read-only. For a tool with zero annotation coverage, this leaves significant gaps in understanding how it operates.

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 extremely concise with just two Chinese terms, making it front-loaded and waste-free. However, the brevity might border on under-specification for non-Chinese agents, slightly reducing clarity. Every term earns its place by indicating data type and source.

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 (real-time data tool with no annotations or output schema), the description is incomplete. It lacks details on return values, error handling, or behavioral constraints. While it states the purpose, it doesn't provide enough context for reliable agent invocation without trial and error.

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 schema description coverage is 100% (empty schema). The description doesn't need to explain parameters, so it meets the baseline of 4 for zero-parameter tools. No additional parameter semantics are required or provided.

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 '实时数据/微博热搜' states the tool provides real-time data about Weibo hot searches, which is a clear purpose. However, it doesn't specify a verb (e.g., 'fetch' or 'retrieve') and doesn't distinguish itself from sibling tools that also provide news/trends from different platforms. The Chinese text might be less accessible to some agents.

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 the 15 sibling tools (e.g., baidu_news, zhihu_news). The description implies it's for Weibo-specific data, but there's no explicit comparison or exclusion criteria. Agents must infer usage based on the platform name alone.

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