bond_corporate_issue_cninfo

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is known. The description adds a source URL and states the return type as pandas.DataFrame, which is useful but minimal. It does not disclose data freshness, pagination, or any site-specific quirks. Without annotations, this would be insufficient, but annotations carry the core safety burden.

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, consisting of a breadcrumb, a URL, and a short docstring. It front-loads the purpose and includes a source link. However, the structure is slightly awkward, mixing a human-readable heading with code-style docstring, and the copy-paste error in the end_date description detracts from clarity. It is not verbose, but not well-polished.

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 describe the returned data structure, but it only says '企业债发行' as a generic return label. It also omits date format details, allowed ranges, timezone considerations, or any limitations of the data source. Given the tool has just two parameters and a simple return, the description leaves the agent with insufficient information for correct invocation and interpretation.

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 attempts to do so with ':param start_date: 开始统计时间' and ':param end_date: 开始统计时间', but both are described as the 'start time', which is clearly an error for end_date. This misleads the agent about the semantics of end_date. Even the start_date description is vague ('统计时间' could mean many things), and no date format constraints beyond the defaults are given.

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 Data Center - Bond Reports - Bond Issuance - Corporate Bond Issuance). Although it lacks an explicit verb like 'fetch' or 'retrieve', the combination of the breadcrumb and return type makes it evident this returns corporate bond issuance data. It distinguishes itself from sibling bond issuance tools (e.g., bond_cov_issue_cninfo, bond_local_government_issue_cninfo) via the specific '企业债发行' subcategory.

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 no guidance on when to use this tool versus alternatives. It does not mention use cases, prerequisites, or exclusions. The only contextual hint is the breadcrumb, which implies it is for corporate bond issuance, but there is no explicit 'when to use this, use X for other bond types' guidance.

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