ChMarketCurReal

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

No annotations are provided, so the description must carry the behavioral burden. 'Realtime snapshot' implies a non-destructive read, which is useful, but nothing is said about permissions, rate limits, latency, or data freshness beyond the word 'realtime'.

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?

Very short and front-loaded, with the scope and the no-arg nature immediately visible. The bilingual duplication of the same sentence is mild redundancy that slightly costs efficiency.

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?

With zero parameters and an output schema present, the description need not explain return values, and it correctly flags the no-argument calling convention. A brief note on what distinguishes the returned index snapshot from sibling market endpoints would make it fully complete.

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?

The tool takes zero parameters, so the schema baseline of 4 applies. 'No arguments' is consistent with the empty properties object and adds a small confirmation rather than new meaning.

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 verb+resource ('realtime snapshot of A-share market indices') and scopes it with exchanges SH/SZ/BJ, which implicitly separates it from siblings like ChStockCurReal, ChConceptCurReal, and ChIndustryCurReal. It never names those alternatives, so full sibling differentiation is not explicit.

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 arguments' tells the agent how to call it, and 'market indices' implies the use case, but there is no explicit statement of when to pick this over the stock-, concept-, or industry-level snapshot siblings. Usage is inferable rather than stated.

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