bond_zh_hs_spot

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so the safety profile is covered. The description adds genuinely useful operational context beyond the annotations: the anti-scraping rate-limit risk ('大量抓取容易封IP') and the return type (pandas.DataFrame), which the agent would not otherwise know.

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 purpose and IP warning are front-loaded, which is good, but the Sphinx-style :param/:type/:return/:rtype block duplicates parameter names and types already present in the input schema, adding some redundancy without much extra signal.

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?

With no output schema, the description responsibly states the return shape (all SH/SZ bond real-time quotes as a DataFrame) and flags the rate-limit risk. For a two-parameter read-only endpoint this is close to complete, missing only pagination bounds or default 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%, so the description must compensate. It labels both params as pagination start/end pages, but adds no format details, valid ranges, or the default values ('1'/'10') that the schema carries. It clarifies intent but is largely restating parameter names.

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 verb+resource: real-time quotes for Shanghai/Shenzhen bonds from Sina Finance, with the source URL. It is distinguishable from siblings like bond_zh_hs_daily (historical) and bond_zh_hs_cov_spot (convertibles), though it does not explicitly name those alternatives.

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 only contextual guidance is the warning that heavy scraping gets the IP blocked. There is no explicit guidance on when to prefer this tool over bond_zh_hs_daily or the other bond spot siblings, nor any stated prerequisites.

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