bond_local_government_issue_cninfo

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint, covering safety traits. The description adds the data source URL and return type (DataFrame), but does not disclose additional behavioral details such as rate limits, pagination, or date range handling.

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 relatively short, but the first line repeats the tool name as a title, and the parameter documentation is inconsistent with a typo. The structure is standard docstring format but could be more polished and error-free.

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?

The tool is a simple data retrieval with two parameters and no output schema, so the description should provide more detail on the returned data structure. It only states '地方债发行' as the return without specifying columns, and the parameter descriptions are incomplete due to the typo.

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 includes doc comments for both parameters, but they are identical and the end_date parameter is incorrectly described as '开始统计时间' (start time) instead of end time. The schema provides defaults implying YYYYMMDD format but no explicit description, so the description both adds and undermines clarity.

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 identifies the resource as CNInfo's thematic statistics for local government bond issuance (地方债发行) with a return type of pandas.DataFrame. It distinguishes from sibling tools like bond_corporate_issue_cninfo and bond_treasure_issue_cninfo by focusing specifically on local government bonds.

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 provides clear context that this is for querying CNInfo data on local government bond issuance with a date range, implying its use for historical bond issuance data. However, it does not explicitly mention alternatives or when not to use this tool, so it lacks exclusions.

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