ChIndustryCurReal

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

No annotations are provided, so the description carries the burden. 'Realtime snapshot' does convey that this is a non-persistent read returning current state, which is genuine behavioral context, but it omits freshness/latency expectations, rate limits, and any auth or entitlement 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?

Two clipped clauses, front-loaded with the resource and scope. The bilingual duplication is somewhat redundant but standard for this tool family and costs little.

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?

An output schema exists, so return values need no explanation, and there are no parameters to document. The description is adequately complete for a no-arg snapshot endpoint, with only usage routing left unstated.

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?

Zero parameters, so the baseline is 4. 'No arguments' confirms the empty schema and removes any doubt about supplying inputs.

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 gives a specific verb+resource in two languages: '获取行业板块实时快照 / Get realtime snapshot of industry sectors.' An agent can identify this as the industry-sector counterpart to ChMarketCurReal/ChConceptCurReal/ChStockCurReal, though it never names those siblings explicitly.

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 when-to-use, when-not-to-use, or alternative routing is offered. The agent must infer from the name alone that this is the industry-scope variant of the realtime family.

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