get_baidu_hot_search

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

There are no annotations provided, so the description carries the full burden of behavioral disclosure. It only says 'get data' and does not mention that results may be cached (despite the use_cache parameter), potential rate limits, network dependency, or what the response looks like. This is minimal disclosure beyond the obvious read operation.

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 concise sentence that directly states the tool's purpose. It is not verbose and the content is front-loaded. However, it is somewhat under-specified for a tool with two parameters, but the conciseness itself is good.

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?

With no output schema and no annotations, the description should explain what data is returned, but it only says 'data' without any structure. It also omits behavior related to the count and cache parameters, and provides no alternative guidance. The description is adequate for the simplest use but incomplete for an agent to fully understand the tool's behavior.

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 100% coverage with descriptions for both parameters (count and use_cache). The tool description adds no parameter information beyond what the schema already provides. Baseline 3 is appropriate because the schema does the heavy lifting.

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 verb (获取/get) and resource (百度热搜榜数据/Baidu hot search data). It distinguishes from get_bilibili_hot by specifying Baidu, but does not clarify how it differs from the sibling search_baidu_hot_search, so it lacks full 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?

The description provides no guidance on when to use this tool versus alternatives such as search_baidu_hot_search or the cache clearing tools. There is no mention of prerequisites, intended use cases, or exclusions. The tool name and schema hint at caching and count, but the description itself gives no usage context.

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