bond_zh_hs_cov_spot

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false. The description adds a non-obvious behavioral trait: the rate-limiting/IP ban risk on heavy scraping, which is not in annotations. Does not cover return format or pagination. Adds valuable context beyond structured data.

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?

Two lines plus :return: and :rtype: annotations. Front-loaded with source and resource. The warning is useful and not overly verbose. Could be slightly more structured but earns its place.

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 no parameters, rich annotations, and no output schema, the description provides sufficient context: what data is returned, from where, and the scraping caveat. It doesn't detail return columns, but the :rtype: tells the agent it's a DataFrame. Complete enough for a no-arg snapshot tool.

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?

Zero parameters, so baseline is 4. The description does not need to explain parameters and correctly focuses on output (:return: real-time data, :rtype: pandas.DataFrame). Schema coverage is 100% but no parameters exist.

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?

States a specific verbless-but-clear resource: '沪深可转债的实时行情数据' (real-time quote data for Shanghai/Shenzhen convertible bonds) with source (新浪财经). Distinguishes from sibling bond_zh_hs_cov_daily (daily) and bond_zh_hs_cov_min (minute) by implying snapshot/spot, but does not explicitly name them. Purpose is clear but lacks explicit sibling differentiation.

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?

Includes an explicit warning about rate-limiting ('大量抓取容易封IP') which indicates when to use it carefully, but does not name alternative tools or state when to use this vs daily/minute variants. Provides context but no exclusions or alternatives.

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