fund_etf_spot_ths

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so the description does not need to restate safety. It adds the source URL and DataFrame return type, but lacks details on date format, pagination, or rate limits. No contradiction.

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?

Description is compact and well-structured, with a title, source URL, and parameter/return docs. It is front-loaded with the essential purpose and does not include filler, though the URL could be seen as extra detail.

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 one-parameter read-only tool, the description covers source, return type, and parameter meaning. However, it omits date format conventions and behavior when date is empty, leaving some ambiguity for an agent invoking the tool.

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?

The schema provides no description for 'date', and the description only gives ':param date: 查询日期' (query date) and type string. It lacks format examples (e.g., YYYYMMDD vs YYYY-MM-DD), default behavior, or whether an empty date means today, providing minimal semantic compensation.

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?

Description clearly identifies the tool as fetching ETF real-time quotes from 同花顺 (THS), with a source URL and return type. It distinguishes from sibling ETF tools by naming THS and ETF spot, though the verb is implied rather than explicit.

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 on when to use this tool versus alternatives. The description does not mention exclusions, preferred contexts, or sibling tools that might be more appropriate for related queries.

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