stock_hsgt_institution_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 the upstream data source and the return type (pandas.DataFrame) but says nothing about rate limits, pagination, or data freshness, which is acceptable but not rich for an open-world web-scraped source.

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?

Structured docstring with source URL, params, and return documented in a front-loaded line. The URL is somewhat extraneous but provides provenance; otherwise every line earns its place.

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, no-required, no-output-schema read tool, the description covers the parameter semantics (including the enum missing from the schema) and the return type. The only real omissions are usage disambiguation against siblings and any behavioral caveats about the scraped source.

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 description coverage is 0%, so the description carries the full burden. It does this well: it enumerates the valid market choices (北向持股/南向持股/沪股通持股/深股通持股), which the schema does not, and gives concrete date-format examples ("20200713"). It does not state the date range defaults or limits.

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 source and resource (东方财富网数据中心-沪深港通持股-每日机构统计) and states the return content: 每日个股统计数据 for a given market and date range. This clearly identifies the tool as HSGT institutional holding statistics. It does not, however, explicitly differentiate itself from close siblings like stock_hsgt_stock_statistics_em or stock_hsgt_hist_em.

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 when-to-use guidance is provided. Given the enormous sibling list containing many HSGT and stock-statistics tools (stock_hsgt_stock_statistics_em, stock_hsgt_hold_stock_em, stock_hsgt_hist_em), the absence of any disambiguation is a meaningful gap.

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