fund_hold_structure_em

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the source URL and return type but does not disclose additional behavioral aspects such as data update frequency, data size, or any potential network dependencies. This is acceptable given the annotations, but the description could enrich the behavioral context.

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 extremely concise, consisting of a title, URL, and return type lines. It is front-loaded with the most important information and contains no filler. However, it reads as a fragment rather than a well-structured sentence, slightly reducing clarity.

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 and no parameters, the description should clarify what the returned DataFrame contains (e.g., columns, scope, whether it covers all funds or specific funds). It only states '持有人结构' without detailing the data shape, leaving the agent uncertain about the exact output. The description is adequate for a simple read-only tool but misses these details.

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 tool has zero parameters, and the input schema is empty. The baseline for 0 params is 4, and the description appropriately focuses on the output rather than inputs. No parameter documentation is needed.

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 tool as providing fund holder structure data from Eastmoney, with the specific resource '规模份额-持有人结构' and a return type of pandas.DataFrame. Though it lacks an explicit verb (e.g., 'retrieves'), the name and description together make the purpose 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?

No guidance is provided on when to use this tool versus the many sibling fund tools. There are no exclusions, prerequisites, or alternative tool references, leaving the agent without context for tool selection.

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