bond_zh_hs_daily

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

Annotations already cover read-only, open-world, idempotent, and non-destructive behavior. The description adds meaningful extra context beyond annotations by noting the scraping/IP-ban risk and documenting the pandas DataFrame return type.

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 front-loaded with the purpose and rate-limit warning, then follows with param/return details. It is reasonably concise, though the source URL and Sphinx-style tags add some boilerplate.

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 one-parameter historical-data tool with no output schema, the description covers the data source, symbol format, scraping risk, and return type. It is complete enough to invoke correctly, though it does not detail the DataFrame columns or date-range 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?

Schema description coverage is 0%, but there is only one parameter and the description fully compensates by explaining that symbol is a Shanghai/Shenzhen bond code and giving a concrete example (e.g., sh010107).

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 states a specific source (新浪财经), resource (沪深债券), and data type (历史行情数据 / 日 K 线数据). It clearly identifies the operation, but it does not explicitly differentiate this tool from many sibling bond-history tools such as bond_zh_hs_cov_daily or bond_zh_cov.

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?

Usage is implied: retrieve historical daily K-line data for a Shanghai/Shenzhen bond. The warning about IP blocking from frequent scraping is useful context, but no explicit when-to-use, when-not-to-use, or sibling alternative guidance is given.

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