fund_etf_category_ths

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

The annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context by naming the data source (同花顺), providing the source URL, and stating the return type is a pandas DataFrame, but it does not add richer behavioral details such as rate limits, authentication requirements, or data freshness.

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 compact and follows a recognizable docstring structure with purpose, URL, parameter, and return sections. It is front-loaded with the data domain, though the URL is not strictly necessary and the opening line duplicates the annotation title.

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 simple two-parameter read-only data retrieval tool, the description covers the source, both parameters, and the return type. However, there is no output schema, and the description does not specify date format or what columns/fields the returned DataFrame contains, leaving meaningful gaps for an agent that needs to interpret the results.

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 must carry the parameter burden. It fully enumerates the symbol choices and clarifies that an empty string means all types, which is valuable semantic detail absent from the schema. It is less complete for date, giving only '查询日期' without format or timezone details, and it does not mention the schema default of symbol="ETF".

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 tool as a Tonghuashun (同花顺) fund data source returning daily net value and real-time quotes, with the symbol parameter defining the fund category. This makes the resource and scope clear, though it reads more like a data page title than an explicit action verb and does not distinguish itself from siblings such as fund_etf_category_sina or fund_etf_spot_ths.

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?

The description gives no guidance on when to use this tool versus alternatives. It only enumerates the symbol choices and notes that "" means all, which describes parameter usage but not task selection.

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