fund_individual_analysis_xq

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

Annotations already declare the tool read-only, idempotent, and non-destructive. The description adds a return type (pandas.DataFrame) and a source URL, which is some useful context, but it does not disclose behaviors like error handling, rate limits, data scoping, or output contents. It does not contradict the 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 compact and logically structured with a title, source URL, and docstring-style parameter/return entries. It is easy to scan and does not contain filler, though the title is repeated and the return description is generic.

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 description is incomplete for a tool with no output schema. It fails to explain what the '基金数据分析' DataFrame actually contains, making it difficult to distinguish from the many other fund analysis tools and to know what to expect from the call. The URL and minimal parameter notes are insufficient.

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 description explains `symbol` as 基金代码 (fund code) and `timeout` as 'choice of None or a positive float number,' which adds meaning beyond the bare schema types. Since the schema properties have no descriptions, this documentation provides necessary context, though it could go further with format or default behavior.

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 states '雪球基金-基金数据分析' and a URL, indicating this is a fund data analysis tool, but it does not specify what specific analysis is performed (e.g., performance, risk, holdings). It also does not differentiate from sibling tools like fund_individual_achievement_xq or fund_individual_basic_info_xq, leaving the purpose somewhat vague.

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 guidance on when to use this tool versus alternatives. The description only provides parameter documentation and return type, with no mention of use cases, prerequisites, or exclusions. This provides no practical selection guidance.

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