fund_info_index_em

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 covered. The description adds the data source URL and the return type (pandas.DataFrame), which is useful context. However, it does not disclose any additional traits like rate limits, pagination, or required authentication, so it adds only marginal behavioral information beyond 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 structured like a docstring with title, URL, parameters, and return type. It is reasonably concise and each section serves a purpose. The URL is somewhat raw and the Chinese title duplicates the tool's subject, but overall it is well-organized and not inflated.

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 simple read-only data retrieval tool with two parameters and no output schema, the description provides the necessary essentials: source URL, parameter choices, and return type. It does not describe the DataFrame's columns, but without an output schema that is less critical. It is adequately complete for an agent to select and use 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 input schema has 0% description coverage and no enums, but the description fully compensates by listing the exact allowed values for both 'symbol' and 'indicator'. It also implicitly provides defaults via the schema. This gives the agent complete knowledge of what values are valid, which is critical for correct invocation.

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 resource (index fund information from Eastmoney/Tiantian) and the specific data category (指数型), and the URL supports it. It lacks an explicit action verb like 'get' or 'fetch', but the intent is obvious. The tool name and description's '指数型' distinguishes it from many sibling fund info tools, though it doesn't explicitly call out those alternatives.

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 is provided on when to use this tool vs. other fund information tools. It does not mention exclusions or alternatives, and the sibling list contains many similar fund_info tools. The description simply states what it does without any decision context.

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