stock_info_sz_change_name

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false. The description adds a source URL and return type (pandas.DataFrame), which are useful but minimal. It does not disclose pagination, error behavior, or data coverage, but given annotations, a score of 3 is appropriate.

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 structured as a docstring with title, URL, parameter, and return sections. Each part contributes useful information, though the title line somewhat repeats the tool name. No unnecessary fluff.

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 single-parameter tool with no output schema, the description covers the source, parameter choices, and return type. However, it lacks details about the returned DataFrame columns, data range, or any examples. It is adequate for simple invocation but not fully comprehensive.

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 thoroughly documents the only parameter 'symbol' with its exact accepted values ('全称变更' and '简称变更') and their mapping to tabs. This is critical information not present in the schema, which only defines a string with a default. Schema coverage is 0%, so the description fully compensates.

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 Shenzhen Stock Exchange name change data, with a source URL and parameter documentation. It is specific enough to distinguish it from broader stock data tools, though it lacks an explicit verb and does not differentiate from siblings like stock_info_change_name.

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?

There is no guidance on when to use this tool versus alternatives. Sibling tools such as stock_info_change_name, stock_info_sh_name_code, and stock_info_sz_name_code exist, but the description provides no comparisons, exclusions, or contextual usage hints.

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