stock_szse_summary

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, covering safety. The description adds modest context by specifying the param is the most recently ended trading day and the return type is a pandas DataFrame. However, it does not disclose other behavioral traits such as pagination, rate limits, or data availability, so it stays at a baseline level.

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 concise, consisting of a title, source URL, parameter documentation, and return type. It avoids unnecessary words and is well-structured as a docstring. While it is brief, it contains no fluff and is easy to parse.

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 read-only tool with one parameter, the description provides the essential information: the source, the date parameter semantics, and the return type. However, it lacks details about what specific categories are included, any prerequisites, or guidance on when to use it among the many sibling tools. Given the simplicity, it is minimally viable but not 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 input schema for 'date' has no description, so the :param date: 最近结束交易日 explanation in the description is essential and helpful. It clarifies the meaning of the parameter, which is all that is needed for a single-parameter tool. This compensates well for the 0% schema description coverage.

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 securities category statistics from the Shenzhen Stock Exchange overview page. The title '深证证券交易所-总貌-证券类别统计' is specific and distinguishes it from similar summary tools like stock_sse_summary or stock_szse_area_summary. While it lacks an explicit verb like 'get' or 'retrieve', the return type and context make the purpose clear.

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 other market summary tools. It does not mention alternatives, exclusions, or conditions under which this tool should be selected. This is a significant gap given the large number of sibling tools dealing with market summaries and statistics.

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