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

Annotations already cover read-only/idempotent/closed-world, and the description adds two genuinely useful facts not in structured fields: data freshness (~10 min refresh) and a per-call billing cost of 1. It still doesn't say what happens with an unmatched concept name or whether 'days' windows beyond available history degrade.

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?

Compact and front-loaded: what it returns, then aggregation semantics, then freshness and cost. The opening clause duplicates the title almost verbatim, a small redundancy, but nothing else is wasted.

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?

Without an output schema, the description still conveys the shape of the result (per-stock mention counts plus institution/KOL mention counts), which is the key missing piece. What remains absent is sibling disambiguation and edge-case behavior for unmatched or sparse concepts.

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 100%, including defaults, bounds and the ≤30-char exact-match constraint on 'concept', so the schema does the heavy lifting. The description only hints at the time window ('最近一段时间') without tying it to the 'days' parameter, adding no new semantics.

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?

States a specific resource (concept-sector heat) and the exact aggregation returned: per-stock mention counts for a given concept. It is distinguishable from get_market_hot_concepts by being concept-scoped, but it never explicitly contrasts with the near-namesake sibling get_stock_concept_heat (the inverse lookup), leaving some ambiguity.

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 on when to use this versus get_stock_concept_heat, get_market_hot_concepts or get_weighted_hot_stocks. The only usage-adjacent statement is the billing note, which tells the agent this call costs money but not when it is the right call.

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