stock_zh_kcb_daily

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds meaningful behavioral context: the IP-ban warning (rate limiting) and the return type as pandas.DataFrame. It does not mention pagination or other side effects, but for a read-only historical data tool, this is sufficient.

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 reasonably concise, front-loading the main purpose and then providing param details. It has a slightly messy structure with the title repeated and a URL, but every part is informative. It earns its place without excessive fluff.

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?

The tool has only two well-documented parameters and a clear return type. The description includes a source URL and a warning about IP bans. It does not detail the exact columns or date range returned, but for a historical data tool of this simplicity, the information is largely complete.

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%, but the description fully compensates by explaining both parameters in detail: symbol (带市场标识的股票代码) and adjust (with all variants: default, qfq, hfq, hfq-factor, qfq-factor). This adds significant meaning beyond the bare schema, making the tool easy to invoke correctly.

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 it retrieves historical market data for 科创板 (STAR Market) stocks from Sina Finance, using specific verbs and resource scope. It distinguishes from sibling tools like stock_zh_a_daily (A-shares daily) and stock_zh_kcb_spot (spot data) by focusing on historical daily data for STAR Market stocks.

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 a clear usage caution ('大量抓取容易封IP' - large-scale scraping may get IP banned), which is useful guidance. However, it does not explicitly mention when to use this tool versus alternatives or exclude specific cases, so it lacks explicit when/when-not guidance but still gives clear context.

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