stock_financial_cash_new_ths

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, covering the safety profile. The description adds the return type (pandas.DataFrame) and the indicator enumeration, which is useful, but says nothing about row shape, units, or whether the data updates live.

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 is front-loaded with the resource name but wastes lines on a bare URL and on ':type' lines that merely repeat the schema's types, and the ':return'/' :rtype' lines restate the title. Adequate but not tight.

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?

No output schema exists, so the description should describe the returned data; it only gives 'pandas.DataFrame' without column semantics. For a two-parameter data-fetch tool whose annotations carry the safety profile, it is minimally sufficient but leaves the return shape opaque.

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%, so the description must carry the burden, and it does list both parameters meaningfully: symbol = stock code and indicator = full choice set {按报告期, 一季度..四季度, 按年度}. This is information absent from the schema, which contains no enum constraints. It stops short of explaining what 按报告期 means versus the quarterly options.

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 resource (同花顺 cash-flow-statement financial indicator) but uses no verb and simply restates the title/return value. Critically, it does not distinguish itself from its near-identical sibling stock_financial_cash_ths, nor from stock_financial_benefit_new_ths / stock_financial_debt_new_ths, so an agent cannot tell why the '_new' variant exists.

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 guidance, no prerequisites, and no mention of alternatives despite many overlapping siblings. The source URL is the only contextual hint, and it is not framed as usage guidance.

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