bond_zh_hs_cov_daily

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

The annotations already declare readOnlyHint, idempotentHint, and destructiveHint, covering the safety profile. The description adds valuable context beyond annotations: the risk of IP ban with large-scale scraping, the source URL, and the return type (pandas DataFrame), which are not present in the annotations.

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 structured as a docstring with a concise first sentence stating the purpose, followed by a URL and parameter/return documentation. It is slightly longer than strictly necessary due to the URL, but the essential information is front-loaded and there is no excess verbosity.

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?

Given the tool's simplicity (one parameter, no output schema), the description is fairly complete: it states the data type returned (daily K-line), the return type (pandas DataFrame), and includes a usage warning. It does not enumerate DataFrame columns, but that is not essential for a straightforward historical data retrieval tool with good annotations.

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?

With schema description coverage at 0%, the description fully compensates by explaining that 'symbol' is the Shanghai/Shenzhen convertible bond code, its type as 'str', and providing an example ('sh010107'). This gives an agent precisely the information needed to invoke the tool 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 that the tool retrieves historical market data for Shanghai/Shenzhen convertible bonds, specifically daily K-line data for a given bond code. This distinguishes it from sibling tools like bond_zh_hs_cov_min (minute data) and bond_zh_hs_cov_spot (spot data), and specifies the return type as a pandas DataFrame.

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 includes a warning that heavy scraping can lead to an IP ban, providing caution about usage frequency. However, it does not explicitly compare with alternative tools or state when to prefer this tool over others, leaving usage context implied by the tool's daily historical nature.

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