fund_info_ths

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, which covers the safety profile. The description adds that it returns a pandas.DataFrame and includes a source URL, but discloses no additional behavioral details like data freshness, rate limits, or the exact content of the returned 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 description is a compact docstring-style entry with the title, a source URL, and parameter/return definitions. It is front-loaded and has no redundant filler. It lacks a natural-language sentence, but remains efficient and easy to scan.

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 single-parameter tool with strong annotations, the description is mostly adequate. However, it does not describe the contents of '基金基本信息', nor any limitations on applicable fund types. Given the very large sibling set with many fund_info tools, additional context on selection and expected output columns would improve completeness.

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 has 0% description coverage for the single parameter 'symbol'. The description compensates by explicitly documenting it as '基金代码' (fund code) with type str, which is essential. However, it does not elaborate on format requirements or valid value ranges beyond the default example.

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 as '基金基本信息' (fund basic info) from THS (10jqka), with a sample URL and param/return definitions. It is specific enough to distinguish from similar fund_info_* tools by source provider. However, it lacks an explicit action verb like 'retrieve' or 'get', relying on a noun phrase.

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 versus the many other fund data tools in the sibling set. There are no mentioned alternatives, prerequisites, or exclusions, leaving the agent without decision support.

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