stock_info_sz_delist

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the return type (pandas.DataFrame) and the source URL (https://www.szse.cn/...), which is useful context, but does not detail other behavioral aspects such as data coverage, pagination, or update frequency.

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 compact docstring with a title, source URL, parameter definition, and return type, all in a standard structured format. Each line serves a purpose, and there is no redundant information.

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 a simple one-parameter, read-only tool, the description adequately covers the essentials: the source, the parameter choices, and the return type (pandas.DataFrame). It lacks examples or details about the DataFrame columns, but given the low complexity and the presence of annotations, this is sufficient.

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 only shows a default value ('终止上市公司') with no description. The description explicitly enumerates the two allowed values for symbol ('暂停上市公司' and '终止上市公司') and specifies the type as str, providing essential semantic information that the schema lacks.

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 tool as providing data on suspended and terminated listed companies from the Shenzhen Stock Exchange (SZSE) by specifying the two categories and including the source URL. The return statement 'return: 暂停上市公司 or 终止上市公司 的数据' makes the purpose explicit, though it lacks a strong imperative verb like 'Get' or 'List'.

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 the two valid values for the symbol parameter, which guides the user on what data each option returns. However, it does not explicitly state when to use this tool versus sibling tools (e.g., stock_info_sh_delist) or provide any contextual guidance on when this tool is appropriate.

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