stock_hot_search_baidu

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, effectively covering the safety profile. The description adds the source URL and return type, but does not disclose edge cases, rate limits, or any deeper behavioral traits beyond what the annotations imply.

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 fairly compact but lacks a structured summary sentence. It leads with a URL and uses docstring-style parameter listings, which conveys necessary information but could be better organized with a concise one-line overview.

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?

For a simple read-only list tool, the description covers the parameters and return type. However, it does not specify the columns in the DataFrame or provide example usage, leaving some ambiguity about the exact output structure.

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?

Schema description coverage is 0%, so the description compensates by documenting all three parameters: symbol with its allowed choices, time with choices and default, and date as '日期'. This adds significant meaning beyond the schema, though the exact date format is only implied by the default value.

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 identifies the resource ('百度股市通-热搜股票') and includes the source URL and return type, making it evident this retrieves Baidu's hot search stock list. However, it lacks an explicit action verb and does not contrast with sibling hot-rank tools like stock_hot_rank_em.

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 alternative hot stock tools. The parameter choices are listed, but there is no mention of alternatives, exclusions, or when to prefer this over similar tools in the sibling set.

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