stock_financial_abstract_ths

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds a source URL and specifies the return type (pandas.DataFrame), but provides no further behavioral details such as data freshness, pagination, or error conditions. It does not contradict annotations.

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 a structured docstring with title, URL, parameters, and return type. It is front-loaded with the title and source, and each section is relevant. The return line repeats the title but is not excessive. It is concise and well-organized for an API docstring.

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?

The tool is simple (2 params) and annotations cover safety, but there is no output schema and the description does not explain the structure or columns of the returned DataFrame. The source URL provides a reference, and the indicator choices hint at data granularity, but an agent may lack clear knowledge of what data rows/columns to expect, especially given the large number of sibling financial data tools.

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 provides no descriptions or enums, and schema coverage is 0%. The description compensates by defining symbol as 股票代码 (stock code) and enumerating the exact allowed values for indicator: "按报告期", "按年度", "按单季度". This adds significant meaning beyond the bare parameter names, though it does not explain the format of the symbol or the semantics of each indicator value.

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 this fetches 同花顺-财务指标-主要指标 (THS financial main indicators) for a given stock symbol, with a source URL. It clearly identifies the resource and source, though it lacks an explicit action verb like 'get' or 'fetch'. It is distinguishable from siblings by the 'ths' suffix and '主要指标' qualifier, but does not explicitly differentiate from similar tools like stock_financial_abstract.

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?

No guidance is provided on when to use this tool versus alternatives such as stock_financial_abstract or stock_financial_abstract_new_ths. The description only lists parameters and return type, with no context about use cases, prerequisites, or exclusions.

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