bond_info_cm

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, so the description's burden is reduced. Yet it adds only the source URL and Chinese parameter labels, not behavioral context like filtering semantics, pagination, or optionality of parameters, beyond the generic return type.

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 a docstring that repeats the title string, includes a URL, and lists parameters without a concise summary sentence. It is not front-loaded with a clear purpose statement, making it less efficient than a well-structured natural language description.

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 an 8-parameter tool with no output schema, the description fails to explain parameter optionality, result format, or typical usage. It only provides the return type as 'pandas.DataFrame' and a vague '信息查询结果', leaving an agent without enough context to invoke it correctly.

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 description provides Chinese glosses for each parameter (e.g., '债券名称' for bond_name, '债券代码' for bond_code), adding semantic meaning beyond the bare schema names. However, it lacks format constraints, examples, or guidance on parameter combinations, so it only partially compensates for the 0% schema description coverage.

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 title '中国外汇交易中心暨全国银行间同业拆借中心-数据-债券信息-信息查询' clearly indicates a bond information query tool from ChinaMoney, providing a specific resource and implied verb. However, it does not differentiate from sibling tools like bond_info_cm_query and bond_info_detail_cm, and lacks a direct sentence stating its functionality.

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 contains only a URL and parameter definitions, with no guidance on when to use this tool versus alternatives, no prerequisites, and no exclusions. An agent cannot determine the intended context from the description alone.

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