stock_financial_debt_ths

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds no behavioral context beyond repeating the title and endpoints – nothing about output shape, data freshness, or rate/scope constraints that the annotations do not already carry.

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, but the block is a docstring dump that repeats '同花顺-财务指标-资产负债表' in the return/rtype lines and includes two raw URLs that add bulk without agent-facing meaning. Wasteful but not obscure.

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 2-parameter read tool with no output schema this is only partially complete: it names the return type (pandas.DataFrame) but not the columns/fields the balance sheet returns, and gives no default behavior of the indicator parameter. Annotations cover the read-only nature, but output expectations remain thin.

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 compensate, and it does: it documents symbol as 股票代码 (str) and indicator as 指标 with the choice set {"按报告期", "按年度"}. Since the schema exposes no enum for indicator, the description is the only place the valid values are stated – a genuine value-add for the agent.

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 a data source (同花顺) and a resource (财务指标-资产负债表, balance-sheet financial indicators), which is more than a pure name restatement. However, it does not distinguish this THS balance-sheet tool from the many sibling balance-sheet tools (e.g. stock_balance_sheet_by_report_em, stock_balance_sheet_by_yearly_em), so an agent cannot tell why it should pick this one.

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 alternative tools. The only context is raw source URLs, which do not instruct the agent about selection or ordering relative to siblings.

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