bond_zh_cov_info_ths

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering the safety profile. The description contributes only the source URL and return type, with no additional behavioral details such as data freshness, network dependency, or pagination. This adds minimal value 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?

The description is compact and front-loaded, with a title, source URL, and return type. It avoids verbosity, though it is too sparse to fully convey the tool's purpose.

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 should clarify the returned data's structure and scope. The phrase '可转债行情' is vague and does not specify DataFrame columns, coverage, or whether it is a snapshot or historical data. For a simple no-parameter tool, the return value is underspecified.

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 input schema is empty with zero parameters, so there is no parametric ambiguity. The description does not need to explain parameters, and the baseline for zero-parameter tools is 4.

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 indicates the tool returns convertible bond market quotes (可转债行情) from the THS data center, with a source URL and pandas DataFrame return type. However, it lacks an explicit verb and does not differentiate it from sibling tools like bond_zh_cov_info or bond_zh_hs_cov_spot beyond the '_ths' source suffix.

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?

No guidance is provided on when to use this tool versus alternatives. It does not state prerequisites, exclusions, or selection criteria, leaving the agent to infer appropriate usage from the name and source only.

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