fund_lof_spot_em

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, covering safety traits. The description adds only the source URL and return type, with no additional behavioral context like data freshness, rate limits, or output structure. It does not contradict annotations, but adds minimal value beyond them.

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 brief and contains only essential elements: title, source URL, return description, and type. It is appropriately short for a zero-parameter tool, though it may be under-specified. Still, it is concise without wasted words.

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 defined, the description should clarify what the returned DataFrame contains and its scope (e.g., all LOF funds, specific columns). It only states :rtype: pandas.DataFrame, leaving the agent unclear about the actual data structure. The URL hints at a grid list but does not confirm coverage or format.

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 schema coverage is effectively 100%, so the description has no parameter burden. The baseline of 4 applies, and no further elaboration is needed since there is nothing to explain.

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 is essentially a restatement of the tool name and title ('东方财富-LOF 实时行情') with only a URL and return type added. It lacks a verb and does not clearly distinguish itself from sibling tools like fund_etf_spot_em, making it closer to a tautology than a clear purpose statement.

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. The description gives no context for selection among the many spot-price tools (e.g., fund_etf_spot_em, stock_zh_a_spot_em), nor any exclusions or preferred scenarios.

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