baidu_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), implying freshness, but doesn't disclose behavioral traits like rate limits, authentication needs, data format, or whether it's read-only. For a tool with no annotations, this leaves significant gaps in understanding how it behaves operationally.

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 phrases. It's front-loaded and wastes no words. However, it could benefit from slightly more structure (e.g., separating purpose from context) to improve clarity without losing efficiency.

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 of news/trending data tools and no annotations or output schema, the description is incomplete. It doesn't explain what the tool returns (e.g., list format, data fields, update frequency), which is critical for an agent to use it correctly. With 16 similar siblings, more context is needed to differentiate and guide usage.

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 has 0 parameters with 100% coverage, so no parameter documentation is needed. The description doesn't add parameter semantics, but with no parameters, the baseline is 4. It appropriately avoids unnecessary parameter details.

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 '实时数据/百度热榜' (real-time data/Baidu hot list) indicates the tool provides real-time data from Baidu's trending topics, which is a specific purpose. However, it doesn't clearly distinguish itself from sibling tools like 'baidu_tieba_news' or 'weibo_news' that also provide news/trending data from different platforms. The purpose is somewhat vague about what type of data or format is returned.

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. With 16 sibling tools, many offering news/trending data from different platforms (e.g., weibo_news, zhihu_news), the description offers no context about when Baidu's hot list would be preferred over other sources. There's no mention of use cases, prerequisites, or exclusions.

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