index_realtime_fund_sw

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

Annotations already declare readOnlyHint and idempotentHint. The description adds the return type (DataFrame), parameter choices, and source URL, but discloses no additional behavioral traits like data freshness or column details. It does not contradict 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 with title, URL, param, and return sections, but the first line repeats the tool's title. It is not overly long but includes redundancy and lacks a concise summary sentence.

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 real-time quote tool with one optional parameter and good annotations, the description provides sufficient context: source, parameter choices, and return type. It doesn't explain data columns or use cases, but the tool's narrow scope makes this acceptable.

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 description explicitly lists the four allowed values for the symbol parameter, which the schema does not provide as an enum. Since schema coverage is 0%, this fully compensates and gives clear semantic meaning to the parameter.

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 states it provides real-time quotes for fund indices from SWS Research, with a source URL. It doesn't use an explicit verb like 'get' or 'fetch,' but '实时行情' implies retrieval. It distinguishes from siblings like index_realtime_sw by specifying fund indices, though not explicitly.

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 on when to use this tool versus alternatives like index_realtime_sw or index_hist_fund_sw. The only usage info is the allowed parameter values, which addresses how to call it, not when.

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