bond_zh_hs_cov_spot

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

Annotations already disclose read-only, idempotent, and non-destructive behavior. The description adds a valuable operational warning: heavy scraping may lead to IP bans, which is crucial for an agent deciding how often to call. It also mentions the return type, adding useful context beyond 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 short but somewhat disorganized, mixing a source URL, a caution, and docstring fragments in a single flow. Phrases like '实时行情数据' repeat, and the structure could be clearer (e.g., separating purpose, caveat, return type).

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 zero-parameter spot data tool, it covers source, scope, return type, and a practical warning. However, it lacks details about the returned DataFrame's columns or data terms, which would help an agent interpret results. No output schema exists to fill this gap.

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?

The tool has zero parameters, and the description correctly indicates it returns all data for the current moment without requiring inputs. There is no need for parameter-level details, and the schema already fully covers the empty parameter set.

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 real-time market data for all Shanghai/Shenzhen convertible bonds from Sina Finance. The phrase '沪深可转债的实时行情数据' and '所有沪深可转债在当前时刻' precisely identifies the resource and scope, distinguishing it from sibling tools like daily or minute-level data.

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 context is implied: this is for current-moment spot data, contrasting with historical daily/min tools. The warning '大量抓取容易封IP' provides a caution about frequency but does not explicitly compare with alternatives or state when to prefer this over siblings.

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