stock_share_hold_change_szse

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

Annotations already declare readOnly, non-destructive, idempotent, and open-world behavior. The description adds the source URL and return type (pandas DataFrame) but does not disclose additional behavioral traits such as rate limits, data currency, or scope limitations. Since annotations are strong, the minimal additional context is acceptable but not rich.

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, with a clear title, source URL, and docstring-style param/return lines. It avoids unnecessary fluff, though the return line largely repeats the title.

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?

With no output schema, the description should elaborate on the returned data structure. It only restates '董监高人员股份变动' and 'pandas.DataFrame' without mentioning columns, date ranges, or other relevant details. For a data retrieval tool, this is a notable gap.

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 'symbol' parameter (0% coverage). The description explains it accepts either '全部' or a specific stock code, adding meaning beyond the schema's bare type. However, it does not specify the exact format for stock codes (e.g., with exchange suffix), leaving some ambiguity.

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 data source (SZSE) and content (director/supervisor/executive share changes) via its title and URL, which distinguishes it from similar SSE/BSE tools. However, it lacks an explicit verb like 'get' or 'list,' relying on the function name and structure to imply retrieval.

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 guidance on when to use this tool versus alternatives like stock_share_hold_change_sse or stock_share_change_cninfo. The parameter description hints at filtering by stock code but does not explain selection criteria or when to choose '全部' vs a specific code.

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