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

Beyond the readOnly/idempotent annotations, the description adds real behavioral context: an update cadence of ~2 minutes, a per-call billing cost of 1, the mention-counting methodology, removal of generic words, and the presence of pure-statistic fields (heat_chg_1d/3d/heat_z20). This meaningfully helps the agent understand freshness and cost.

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 purpose and scope are front-loaded in the first clause, and each subsequent sentence adds substantive detail (methodology, stats, freshness, billing). It is somewhat dense with stacked parentheticals but no sentence 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?

All three parameters are documented, and although there is no output schema, the description names key returned fields (heat_chg_1d/3d, heat_z20), the sort order, and the exclusion of generic words. Freshness and billing are also covered, making it adequately complete for a read-only list tool.

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 100%, so limit, window, and min_score are already fully documented, including enum values and the min_score scoring range. The description only restates the window span (1h~3d) and adds no syntax or usage nuance beyond the schema, so baseline 3 applies.

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 verb+resource: market-wide concept-sector hot ranking, counting mentions and institution/KOL coverage, sorted high to low with generic terms removed. It is clear what the tool returns and how it is ordered. It does not explicitly distinguish itself from near-siblings like get_concept_stock_heat or get_stock_concept_heat, leaving the agent to infer market-wide vs. per-concept scope.

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 context is implied by the 'market-wide hot ranking' framing and the window range, but there is no explicit when-to-use/when-not guidance and no named alternative. The agent must infer the choice against the many sibling heat tools itself.

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