stock_financial_cash_ths

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

Annotations already declare readOnly, idempotent, openWorld, and non-destructive behavior. The description adds source URLs and return type (pandas.DataFrame), but does not disclose rate limits, authentication needs, or pagination.

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 brief but front-loads a title and two URLs before parameter documentation. Some lines, such as type declarations, duplicate schema information, making it less efficiently structured.

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 simple read-only financial data retrieval tool with rich annotations, the description covers the source, parameters, and return type. However, with no output schema, it does not describe the returned DataFrame's columns or content beyond the title.

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?

With 0% schema description coverage, the description supplies meanings for both parameters: symbol as stock code and indicator with its three allowed values. This compensates for the missing schema descriptions, though format details for symbol are not given.

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 specific resource ('同花顺-财务指标-现金流量表') and includes the source URL, making the retrieval target clear. It does not distinguish this tool from sibling tools such as stock_financial_cash_new_ths, but the resource is specific enough for selection.

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, nor any prerequisites or exclusions. The indicator choices are listed but do not explain usage context.

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