stock_shareholder_change_ths

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

Annotations already declare readOnly, idempotent, and non-destructive behavior. The description adds a source URL and return type (pandas.DataFrame), providing some context, but doesn't mention data freshness, scraping limits, or other behavioral nuances.

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 docstring is compact, containing a title, URL, param, and return lines. It is well-structured but the title and return lines are redundant, and the purpose is stated only implicitly.

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?

The description provides the return type and a source URL, but no column details or data structure. For a DataFrame-returning tool, the agent cannot infer what fields are included, making the description incomplete for robust invocation.

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 includes ':param symbol: 股票代码' (stock code), which minimally clarifies the parameter beyond the schema's type/string. However, it lacks format details, accepted exchange values, or examples beyond the default '688981' already present in the schema.

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 identifies the data source (同花顺/THS) and topic (股东持股变动/shareholder shareholding changes) with a URL. However, it lacks an explicit verb and does not differentiate from sibling tools like stock_share_change_cninfo.

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 is provided on when to use this tool versus alternatives, nor any exclusions or prerequisites. The description only restates the tool's scope without contextualizing its use.

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