fund_etf_scale_sse

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and non-destructive behavior, lowering the bar. The description adds the useful behavioral note that an empty date returns the latest data, but does not describe return shape, pagination, or freshness beyond that.

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 docstring-style layout is front-loaded with the source path and URL, then a compact param/return block. The breadcrumb path is somewhat verbose but conveys provenance, and no sentence is wasted.

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 single-parameter read-only fetch with no output schema, the description supplies the source, the parameter format/default and the return type (pandas.DataFrame of ETF share/scale data). Annotations cover the safety profile, so what remains is adequate to call it correctly.

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 description coverage is 0% for the sole 'date' parameter, so the description carries the burden and does so: it explains the format ("20250115") and the default-empty-returns-latest behavior. This meaningfully compensates for the missing schema description.

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 names the source (Shanghai Stock Exchange), the resource (ETF fund scale list) and provides the canonical URL, so the agent knows this retrieves SSE ETF scale data. It distinguishes from the SZSE counterpart mainly through the naming/breadcrumb rather than explicit text, so it is clear but not sibling-differentiating in prose.

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?

There is no statement of when to use this over the many sibling fund/ETF tools (e.g. fund_etf_scale_szse, fund_etf_spot_em). The only usage hint is the date default behavior, which is parameter guidance rather than selection guidance.

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