get_qhkc_index_trend

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered without the description. The description adds real context beyond that by showing the returned entity (per-broker money/open_order by variety), but it says nothing about rate limits, auth, or the freshness/completeness of the data.

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 purpose is front-loaded, but roughly eighty percent of the text is a raw 34-row DataFrame dump that repeats what a hypothetical return schema would convey. It bloats the definition and pushes actionable guidance out of view.

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?

With no output schema, the sample table does legitimately communicate the shape of the return (broker, grade, money, open_order, variety), which is the tool's strongest completeness contribution. But defaults ('奇货商品', the qhkch.com URL) and any usage guidance are absent, so an agent still has gaps.

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 load. It does supply the candidate values for `name` (the eleven index categories), which is the single most important semantic detail. However, `:param name: None` is a literal non-documentation, and `url` is only glossed as '网址' with no note that it is a rarely-changed endpoint override, so half the semantics are missing.

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?

States the specific source and resource: QHKCH index trend / big-money movement (大资金动向), and enumerates the eleven valid index categories, which lets an agent distinguish it from siblings like get_qhkc_index_profit_loss or get_qhkc_fund_position. The English-less title makes it less immediately scannable, but the intent is unambiguous.

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?

There is no statement of when to use this tool versus the many related QHKCH siblings (fund_bs, fund_money_change, index_profit_loss). No prerequisites, no exclusions, no context. The reader must infer everything from the name and category list.

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