获取单只股票行情

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false. The description adds context beyond those by spelling out the data returned (price, change%, PE/PB, market cap, dividend yield, turnover rate) and the real-time nature, giving the agent a clear behavioral expectation without contradicting annotations.

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?

One concise, front-loaded sentence. It states the core purpose first and then efficiently lists the important returned fields. There is no repetition, fluff, or ambiguity.

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 single-parameter, read-only tool with an existing output schema, the description combined with the schema is complete. It identifies the input format, the single-stock scope, the real-time nature, and representative output fields, so an agent has everything needed to invoke it correctly.

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%: the single required parameter symbol is fully documented with format examples (A-shares SH/SZ, HK 00700, US AAPL). The description adds no additional parameter semantics beyond what the schema already provides, so the baseline of 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 states a specific verb ('获取'), a specific resource ('单只股票'), and enumerates the key returned metrics (现价、涨跌幅、PE/PB、市值、股息率、换手率). The '单只' qualifier distinguishes this tool from sibling get_batch_quotes, so its purpose is clear and differentiable.

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?

The description makes the use case clear: retrieve a real-time quote for a single stock. It does not explicitly point to alternatives like get_batch_quotes or say when not to use it, but the singular scope ('单只') provides enough contextual guidance for an agent to select it appropriately.

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