bond_china_yield

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. The description adds the one-year date-window limit and return type (pandas.DataFrame), but omits auth/rate-limit or column-level behavior.

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 title, note, and Sphinx-style fields are front-loaded and mostly relevant, but the two raw URLs and repeated return phrasing add noise without helping invocation.

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?

There is no output schema, so the description should be more complete about return values, yet it only gives rtype pandas.DataFrame. It does provide the key date-range constraint, which is enough for basic invocation but leaves gaps.

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 carry parameter meaning. It documents both start_date and end_date and the one-year constraint, but the wording about each date returning a one-year window is confusing and no date format (YYYYMMDD vs YYYY-MM-DD) is specified.

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?

Names the source (中国债券信息网) and resource (国债及其他债券收益率曲线), so the agent knows it fetches bond yield-curve data. It does not explicitly differentiate from sibling bond tools such as bond_china_close_return_map, but the resource is specific enough.

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 a concrete constraint (end_date - start_date should be less than one year) and parameter behavior, implying a date-range query. It gives no explicit when-to-use guidance or alternatives versus sibling bond/macro tools.

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