stock_zh_a_gdhs

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety behavior needs no restating. The description adds modest value by naming the source (东方财富网数据中心) and the return type (pandas.DataFrame). It does not describe columns, coverage, or update cadence, so it adds context but not rich behavior.

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 Sphinx-style docstring is compact and front-loads the source and resource before the param block. The bare URL adds little beyond the already-named source, and the `:type`/`:rtype` lines are mechanical padding, but it is not bloated.

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 read tool with no output schema and no required params, the description covers what the tool returns and how to format the one argument, which is adequate. It still omits any routing guidance relative to stock_zh_a_gdhs_detail_em and gives no sense of the returned dataframe's shape or coverage.

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?

Schema coverage is 0% (the single symbol param has only a default and no description or enum), so the description carries the full burden. It usefully specifies the accepted values {"最新", "每个季度末"} and the required `20230930` date format for quarterly input. That meaningfully exceeds what the schema provides.

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 names a specific resource (股东户数/股东户数 data from Eastmoney's data center) and implies retrieval, so the agent knows what data comes back. However, it uses no explicit verb, and it does not distinguish itself from the closely related sibling stock_zh_a_gdhs_detail_em. Purpose is inferable but not perfectly disambiguated.

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 statement of when to use this tool, when not to, or what alternatives exist for shareholder-count data. The sibling stock_zh_a_gdhs_detail_em is never mentioned, leaving the agent to guess which to pick. Only the parameter format is hinted at, which is not usage guidance.

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