bond_zh_hs_daily

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

Annotations already indicate read-only and idempotent behavior. The description adds a rate-limit warning, but this also appears in the annotations title, so it does not add much beyond what is already structurally provided. No other behavioral traits such as data freshness or pagination are described.

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 docstring with a concise summary, source URL, parameter and return type explanations. It is well-structured and not overly verbose, with each line serving a purpose. The front-loaded one-liner gives immediate clarity.

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?

There is no output schema, and the description only states the return is a pandas DataFrame of daily K-line data without specifying columns or date range. The rate-limit warning is helpful, but more detail about the output structure and data scope would make the tool easier to invoke correctly.

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 has no property descriptions (0% coverage), so the description must compensate. It explains 'symbol' as a Shanghai/Shenzhen bond code and provides an example (sh010107), which is meaningful guidance for constructing the parameter. This goes beyond the bare schema definition.

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 historical daily K-line data for Shanghai/Shenzhen bonds from Sina Finance (新浪财经-债券-沪深债券-历史行情数据), with an example symbol and return type. This specific verb-resource-scope combination distinguishes it from sibling tools like bond_zh_hs_spot and bond_zh_hs_cov_daily.

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 implies usage for historical daily bond data but does not explicitly state when to use this tool over alternatives. It includes a rate-limit warning ('大量抓取容易封 IP'), which is a usage caution, but lacks exclusions or mention of sibling tools for real-time or convertible bond data.

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