fund_etf_spot_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 no behavioral context beyond the return type (pandas.DataFrame) and a source URL; it does not disclose pagination, data freshness, or column details.

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 short, containing only a title, a URL, and return type info. It is concise without redundant explanations, though the structure is minimal and lacks an explicit overview.

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 offers almost no detail about the contents of the returned DataFrame. With no output schema, the agent is left without information about columns, data formatting, or any limitations, making it insufficient for non-trivial use cases.

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?

With zero parameters, the schema coverage is trivially 100%. The baseline for 0-param tools is 4, and there is no need for the description to explain parameter meanings.

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 '东方财富-ETF 实时行情' clearly identifies the resource (ETF) and data source (East Money) and indicates real-time quotes. It is concise and specific, though it lacks an explicit verb like 'fetch' or 'list', which is typical for data-retrieval tools.

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 alternatives. There is no mention of exclusions, prerequisites, or scenarios where this tool is preferred over sibling tools like fund_lof_spot_em or fund_etf_spot_ths.

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