stock_hsgt_individual_em

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds only the return type (DataFrame) and a source URL, but does not disclose data scope, historical depth, or any other behavioral traits. It does not contradict the annotations, but adds minimal value beyond them.

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 a compact, structured docstring with a URL, parameter, and return section. It is not verbose and contains no filler. Some redundancy exists between the title in the annotations and the first line, but overall it is appropriately sized.

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 tool with one optional parameter and no output schema, the description is thin. It does not explain what columns the returned DataFrame contains, whether it returns historical or current holdings, or how it differs from the many sibling stock-connect tools. The URL hint is useful but insufficient for complete agent comprehension.

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?

With 0% schema description coverage, the description's parameter documentation (':param symbol: 股票代码', ':type symbol: str') provides essential meaning that the schema lacks. It clarifies that symbol is a stock code string, but does not specify format constraints, leading zeros, or the default behavior beyond the schema's default value.

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 that the tool returns '具体股票-沪深港通持股' (specific stock's Stock Connect holdings) and provides a URL example. It identifies the resource (a specific stock) and the data type (holdings). However, it does not explicitly distinguish itself from sibling tools like stock_hsgt_individual_detail_em or stock_hsgt_hold_stock_em, relying on the name for differentiation.

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. The description is purely declarative, with no mention of use cases, prerequisites, or exclusions. Given the many related stock-connect tools in the sibling list, this is a significant gap.

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