stock_hsgt_stock_statistics_em

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds useful context (remote data source URL, accepted symbol values, date format) but does not describe pagination, row volume, or freshness of the data.

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 source URL and symbol routing are front-loaded, but the Sphinx :param:/:type: block repeats information the JSON schema already encodes (names and types), adding length without new meaning. Structure is conventional rather than optimized.

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 3-parameter query with no output schema, the description names the return type (pandas.DataFrame) but not its columns or granularity beyond 'daily per-stock statistics', and it references a market parameter the caller cannot actually supply. Adequate but leaves real gaps.

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%, so the description carries the burden and mostly does: it enumerates symbol choices {"北向持股", "南向持股"} and gives concrete date format examples ("20200713"). It is undercut by documenting a market=001/003 parameter that does not exist in the schema, which can misdirect the agent.

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 states a concrete verb (fetch daily per-stock statistics) and resource (East Money HSGT holdings data), and the source URL confirms the exact dataset. It does not name or contrast itself with sibling tools such as stock_hsgt_institution_statistics_em or stock_hsgt_hold_stock_em, so an agent must infer the boundary itself.

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 when-to-use guidance and no named alternative. The only routing hints are market=001/003 labels and the source URL, which tell you nothing about when this tool should be chosen over the many other hsgt/stock_* siblings.

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