get_stock_concepts

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

With no annotations, the description does substantial behavioral work: it specifies THS category coverage, Eastmoney's IS_PRECISE=1 restriction, preservation of taxonomy and raw evidence, and the lack of filtering or deduplication. It does not explain caching, partial results when page or time limits are reached, or error behavior, so it is not exhaustive.

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 resource, while each subsequent statement adds source scope, preservation behavior, operational limits, or processing caveats. Its telegraphic style is dense but contains essentially no filler.

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 six-parameter tool with no annotations or output schema, the core source and transformation behavior is well covered, but important invocation and result details remain missing. In particular, code, format, and no_cache semantics, output shape, and truncation or partial-result behavior are not explained.

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?

Despite 0% schema description coverage, it documents the three source values and the valid ranges for max_pages and max_seconds. It adds nothing about the required code's accepted syntax, format's supported values, or no_cache's effect, leaving half of the parameters underexplained.

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 identifies the resource as company concepts plus provider-written reasons, and the THS/Eastmoney details give it a concrete retrieval scope. It does not explicitly distinguish the tool from siblings such as get_stock_industry or get_industry_info, so it is clear but not fully differentiating.

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?

Usage is implied by the emphasis on provider-native concepts, raw records, and the absence of semantic filtering or cross-source deduplication. There is no explicit when-to-use or when-not guidance, nor a named alternative for agents choosing among concept, industry, and board tools.

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