stock_financial_debt_new_ths

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

Annotations indicate readOnlyHint=true, idempotentHint=true, destructiveHint=false, so safety profile is clear. Description adds the data source (THS) and the financial statement type (balance sheet), and includes a URL for reference. It doesn't describe rate limits or return format details, but the annotations cover the key behavioral traits.

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 and front-loaded with the title. The use of a URL and docstring-style parameters is efficient, though the URL takes up space and could be considered noise. Still, it's short and focused.

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 data retrieval tool with 2 optional params and read-only annotations, the description covers the essential: source, type of data, and parameter meaning. No output schema exists, but the return type is stated as pandas.DataFrame. The tool is relatively simple compared to others, and the description is adequate for an agent to use it correctly.

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 coverage is 0%, so the description must compensate. It lists two parameters: symbol (stock code) and indicator (choice of 按报告期 or 按年度). This adds meaning: symbol is a stock code, indicator is a choice between 'by report period' and 'by year'. However, it doesn't provide examples or defaults beyond the schema's default values.

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 clearly states it's for THS (同花顺) financial debt/balance sheet data. The title also confirms it's about the balance sheet. It uses a specific verb and resource, and the URL helps identify the data source, though it doesn't explicitly differentiate from siblings like stock_zcfz_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?

Implied usage: it's a data retrieval tool for balance sheet data from THS. The description's URL and title suggest when to use it, but there's no explicit guidance on when to use this vs alternatives like stock_zcfz_em (balance sheet from EM) or stock_financial_debt_ths. Sibling tools exist but no differentiation is provided.

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