stock_financial_abstract_ths

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, covering the safety profile. The description adds essentially nothing beyond that – no return-shape context (beyond a generic pandas.DataFrame rtype), no data-scope caveats, no data-source latency or authentication notes. It does not contradict the annotations, but it contributes no behavioral context of its own.

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?

It is a compact docstring, but the title phrase is duplicated in both the opening line and the :return: line, and a bare webpage URL adds little. Layout is front-loaded but includes redundant, non-earning text.

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 two-parameter, read-only indicator-data lookup with annotations already covering safety and no output schema required, the description supplies the parameter meanings and the indicator enum values. The remaining gap – sibling differentiation – is a purpose/usage issue scored elsewhere, so completeness for actually calling the tool is adequate.

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 parameter burden, and it does partially: it labels symbol as 股票代码 (stock code) and lists the indicator choices {'按报告期','按年度','按单季度'}, which is not encoded as an enum in the schema. This is genuinely additive, but it omits format expectations for symbol and does not mention the schema 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 states the resource ('同花顺-财务指标-主要指标' – Tonghuashun financial main indicators) but is essentially a restatement of the tool title, with no verb or scope statement. Critically, it does not distinguish this from the many sibling tools such as stock_financial_abstract, stock_financial_abstract_new_ths, stock_financial_analysis_indicator, and stock_financial_analysis_indicator_em. Purpose is inferable but vague.

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 mention of when not to use it, and no named alternatives among the near-identical 'financial abstract' siblings. The only directional content is a bare URL. Nothing tells the agent why it should pick this over stock_financial_abstract_new_ths or stock_financial_analysis_indicator.

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