baidu_tieba_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 states '实时数据' (real-time data), which implies freshness but doesn't disclose behavioral traits like rate limits, authentication needs, data format, or pagination. For a tool with zero annotation coverage, this leaves significant gaps in understanding how the tool behaves.

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 at just two Chinese phrases ('实时数据' and '百度贴吧热榜'), with zero wasted words. It's front-loaded with the key information (real-time data from Baidu Tieba hot list). Every element earns its place by specifying both the 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 no annotations, no output schema, and 16 similar sibling tools, the description is incomplete. It doesn't explain what the tool returns (e.g., list format, fields included), how fresh the data is beyond 'real-time', or how it differs from other news-fetching tools. For a tool in this crowded context, more completeness 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 lack of inputs. The description doesn't need to add parameter semantics, and it doesn't contradict the schema. Baseline 4 is appropriate for zero-parameter tools where the schema already indicates no inputs required.

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 the tool fetches real-time data from Baidu Tieba's trending/hot list. It specifies the resource (Baidu Tieba hot list) and implies the action (fetch/retrieve). However, it doesn't explicitly distinguish from sibling tools like 'baidu_news' or 'weibo_news' beyond the platform name, missing sibling differentiation.

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. The description doesn't mention any context, prerequisites, or exclusions. With 16 sibling tools all appearing to fetch news/trending data from different platforms, the agent receives no help in selecting the right tool for a given scenario.

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