get_hk_quotes

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

Annotations already declare readOnlyHint=true, so the agent knows this is a safe read operation. The description adds the specific return fields (latest price, change percent, volume), which is useful context. However, it does not disclose any potential rate limits, error behavior, or whether the tool supports batch quotes beyond the schema's array parameter.

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 a single, front-loaded sentence that states the core function and return fields. No wasted words or redundant information. Highly concise and structured.

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 simple single-parameter tool with high schema coverage and read-only annotations, the description is sufficiently complete. It names the market, the type of data (real-time quotes), and the returned fields. The absence of an output schema is mitigated by the explicit listing of return fields. A minor gap is the lack of distinction from get_all_hk_quotes, but this tool clearly requires specific codes.

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% and the parameter description already explains the format with an example (['00700','09988']). The tool description adds no additional parameter semantics beyond the schema, so the baseline score of 3 is appropriate.

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 clearly states the tool fetches Hong Kong stock real-time quotes and lists the key returned fields (latest price, change percent, volume). It distinguishes from US/A-share quote tools, but does not explicitly differentiate from sibling get_all_hk_quotes, which also covers HK quotes.

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 is provided about when to use this tool versus alternatives. There is no mention of exclusions or references to sibling tools like get_all_hk_quotes or get_hk_history_kline. The agent must infer usage from the name and schema.

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