stock_financial_cash_ths

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

Annotations already declare the tool safe (readOnlyHint=true, idempotentHint=true, destructiveHint=false), so the bar for additional disclosure is lower. The description adds only that it returns a pandas DataFrame, but gives no extra behavioral context such as data coverage, rate limits, or error behavior, which is a minimal addition.

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 compact but repetitive, repeating '同花顺-财务指标-现金流量表' three times and including raw URLs and a Python docstring format. It does not front-load a clear action sentence, and some content (e.g., the hardcoded example symbol 000063 in URLs) is not explained.

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?

With no output schema, the description fails to explain what the returned DataFrame contains (columns, index, etc.). It also does not specify which stocks are supported (e.g., A-shares only) or any limitations, so an agent cannot fully judge if it meets a user's needs. The tool is simple, but the description lacks key contextual details.

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 input schema has no descriptions (0% coverage), so the description's parameter docs add crucial meaning: symbol is 股票代码 (stock code) and indicator specifies the choice set {按报告期, 按单季度, 按年度}. This compensates for the schema gap, though it lacks format validation or explicit examples beyond the defaults.

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 tool as retrieving the cash flow statement from 同花顺 (TongHuaShun) via the title and URLs, making the resource clear. However, it lacks an explicit verb like 'fetch' or 'get', and does not distinguish itself from closely related sibling tools such as stock_financial_cash_new_ths or stock_cash_flow_sheet_by_report_em.

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 guidance on when to use this tool versus alternatives. The description does not mention supported markets (e.g., A-shares), prerequisites, or exclusions, so an agent cannot determine its appropriate context beyond the implicit source and financial statement type.

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