stock_szse_area_summary

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is known. The description adds that it returns a pandas DataFrame and provides a source URL, but it does not disclose other behavioral traits such as data frequency, sorting, or error handling. This is minimal but non-contradictory.

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: a title line, a source URL, and docstring-style parameter/return documentation. No redundant text, and the structure is logical. It earns a 4 rather than 5 because the param format detail is incomplete, but it is still efficient.

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?

Given there is no output schema and only one parameter, the description is reasonably complete: it states the purpose, parameter meaning, and return type. However, it lacks explicit usage context (when to choose this over sibling summary tools) and precise date format specification, leaving some gaps for an agent.

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 schema provides no description for the 'date' parameter (0% coverage). The description compensates by stating it is the 'most recent trading day' and a string type, with a default '202203' hinting at a YYYYMM format. However, the format is ambiguous (month vs. day), and the description does not clarify the exact expected format.

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 states '深证证券交易所-总貌-地区交易排序' (Shenzhen Stock Exchange - Overview - Regional Trading Ranking), which identifies the specific data resource. It also includes the source URL and explicitly returns a pandas DataFrame of regional trading rankings, distinguishing it from sibling tools like stock_szse_summary or stock_szse_sector_summary.

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?

No explicit guidance is provided on when to use this tool versus alternatives. The only hint is the date parameter description ('最近结束交易日'), but there is no mention of exclusions or preferred use cases compared to similar summary tools.

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