fund_etf_scale_sse

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

Annotations already declare read-only, idempotent, non-destructive behavior. The description adds that an empty date returns the latest data and that the return is a pandas DataFrame. It does not disclose details like data structure or rate limits, but is consistent with 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 begins with a repetitive breadcrumb and URL, then uses structured param/return docs. It is moderately concise but not front-loaded with a clear, concise purpose statement.

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 one-parameter tool without an output schema, the description provides the data source, parameter format, and return type. However, it does not detail the DataFrame columns, whether multiple ETFs are returned, or any quirks, leaving some gaps.

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?

Schema coverage is 0%, so the description must compensate. It explains the 'date' parameter's meaning (统计日期), format ('20250115'), and default behavior (empty returns latest data). This adds significant value beyond the bare schema.

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 identifies the resource as SSE ETF product scale data, with a URL and return type indicating it provides ETF fund share data. It implies the tool's purpose clearly, though it lacks an explicit verb like 'get' or 'fetch'.

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?

The description indicates the data source is the Shanghai Stock Exchange (上海证券交易所), which implies when to use it, but it does not explicitly contrast with alternative tools like fund_etf_scale_szse or state exclusions. Usage context is clear but not fully elaborated.

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