fund_scale_daily_szse

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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so safety is covered. The description adds genuinely useful behavior: ranges longer than 6 months return an empty DataFrame with headers, which tells the agent how failure manifests.

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 purpose is front-loaded and the constraint is well placed at the end, but the Sphinx :param:/:type: directives restate parameter types already present in the JSON schema, adding noise without new meaning for an agent.

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 3-parameter read-only tool with no output schema, the description covers inputs, formats, valid values, and the range-limit failure mode. Only the absence of sibling-routing guidance keeps it from being fully complete.

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% and there are no enums in the schema, so the description carries the full burden — and it does: date format example ("20260401") for both date params and the symbol choice set {ETF, LOF, REITS} that the schema omits entirely.

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?

Names a specific source, resource, and cadence: Shenzhen Stock Exchange fund product scale daily data, with a source URL anchoring it. It is distinguishable from Sina-sourced siblings like fund_scale_close_sina, though it does not explicitly contrast itself with them.

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 when-to-use / when-not guidance or named alternatives among the many fund_scale and fund_etf siblings. The 6-month range limit is a usage constraint, which partially compensates, but routing guidance is absent.

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