stock_board_industry_index_ths

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds a source URL and return type (pandas.DataFrame) but no further behavioral details such as data frequency, pagination, or auth requirements.

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 short and not overly verbose, but it is structured like a docstring with a URL and parameter stubs rather than a concise agent-facing summary. It repeats the title without providing a clearer action statement, yet it does not waste words.

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 3-parameter tool with no output schema, the description fails to explain the output columns, symbol format, data frequency, or what the DataFrame contains. While annotations cover safety, the missing operational details leave the agent under-informed for correct invocation.

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 description's parameter docs are minimal translations ('start time', 'end time', 'index data') that add little beyond the schema's property names and defaults. The symbol parameter format is ambiguous (e.g., code vs. name) and the example URL uses a code while the default is a name, creating confusion.

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 names the resource (同花顺行业板块指数数据) and includes a URL and return type, indicating it retrieves industry index data. However, it lacks an explicit action verb and does not differentiate from sibling tools like stock_board_industry_info_ths or stock_board_industry_hist_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?

There is no guidance on when to use this tool versus alternatives. No context about preferred use cases, alternatives, or exclusions is provided, leaving the agent without direction on tool selection.

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