fund_etf_category_ths

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is established. The description adds that it returns a pandas DataFrame and specifies parameter choices, but does not disclose behaviors like rate limits, data availability by date, or what happens with an empty date. No contradiction with annotations.

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 structured docstring with a title, source URL, parameter documentation, and return type. It is concise and each section serves a purpose. The URL provides verification context without unnecessary verbosity.

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?

The tool is simple, but there is no output schema and the return description only says 'pandas.DataFrame' without column details. The phrase '每日净值-实时行情' (daily NAV - real-time quotes) is somewhat ambiguous about whether it returns both daily NAV and real-time quotes. The parameter coverage is good, but the absence of return structure makes it only minimally complete.

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. The 'symbol' parameter is thoroughly documented with an explicit choice list and the meaning of empty string as 'all'. The 'date' parameter is only described as 'query date' without format or default explanation, though the schema shows a default of ''. This adds significant meaning beyond the bare schema.

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 identifies the tool as providing real-time quotes for fund categories from the THS data center, with a source URL. It specifies the resource (fund data, daily NAV, real-time quotes) and distinguishes itself via 'category' in the name, though it does not explicitly state a verb like 'get' or 'fetch'. It is not a tautology and is understandable.

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 implies usage through the parameter docs (symbol category and date), but does not explicitly state when to use this tool versus alternatives like fund_etf_spot_ths or fund_etf_category_sina. There are no exclusions or context about typical use cases, so guidance is only implied.

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