ETF底层资产：获取ETF底层重仓行业、重仓股票、重仓债券

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

With no annotations provided, the description carries the full burden of behavioral disclosure but provides none. It doesn't indicate whether this is a read-only operation, what permissions might be required, whether it has rate limits, what format the output takes, or any behavioral characteristics. The description is merely a restatement of the title with no operational information.

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?

While technically concise (a single phrase), this represents under-specification rather than effective conciseness. The description doesn't front-load important information or provide any meaningful structure - it's just a repetition of the title. Every sentence should earn its place, but here there's essentially no sentence, just a label restatement.

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?

Given that this tool has no annotations, a single parameter with good schema coverage, and an output schema exists, the description is incomplete. For a tool that presumably returns detailed asset holdings data, the description should at minimum clarify what '重仓' (heavy holdings) means, what time period the data covers, and the scope of the returned information. The existence of an output schema helps, but the description itself is inadequate for understanding the tool's purpose and behavior.

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 description coverage is 100% with the single parameter 'query' well-documented as 'ETF基金代码或ETF基金名称' (ETF fund code or ETF fund name). The description adds no parameter information beyond what's already in the schema. With high schema coverage, the baseline score of 3 is appropriate since the schema does the heavy lifting, though the description provides zero additional parameter context.

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?

Tautological: description restates name/title.

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 provides absolutely no guidance about when to use this tool versus alternatives. There's no mention of when this tool is appropriate, what distinguishes it from similar tools like 'fundUnderAssets' or 'etfBasicInfo', or any prerequisites or context for its use. The description is identical to the title and offers zero usage context.

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