stock_zh_index_value_csindex

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds source URL and return type pandas.DataFrame, but it does not describe permissions, rate limits, failure behavior, or returned valuation fields.

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 front-loads the source and data type. The Sphinx-style type/return tags and the long URL are somewhat boilerplate, but they do not significantly hurt readability or size.

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 one-parameter read-only data-fetch tool with existing annotations, the description is mostly adequate, but with no output schema it should say more about the returned valuation data, such as columns or period coverage, instead of only saying pandas.DataFrame.

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 parameter meaning. It does explain that symbol is an index code and gives an example, H30374, which is sufficient for a single-parameter fetch, though it does not mention the default or other valid index code formats.

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 specific source and data type: CSIndex (中证指数) index valuation data (指数估值数据). It is clear enough for an agent to recognize the resource, but it does not use an explicit retrieval verb and does not distinguish itself from other index/valuation siblings.

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 alternatives, and no conditions that would route an agent between this tool and other index or valuation tools. The description assumes the agent already knows why to call this specific CSIndex valuation endpoint.

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