获取股票实时行情

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

No annotations provided, so description carries full burden. It discloses auto failover across data sources (behavioral trait) but does not specify rate limits, permissions, data delay, or return format. Adequate but not detailed for a real-time feed.

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 sentences in Chinese, concise and front-loaded. No wasted words; every part provides essential information.

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?

Given no output schema, description reasonably covers returned fields (price, change, volume, turnover, PE). It omits timestamp and other common fields like open/high/low/close, and does not detail failover behavior. Mostly complete for its complexity.

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% with good descriptions for both symbol and market. The description adds value by listing output fields (price, change, volume, etc.), but does not enhance understanding of input parameters beyond schema. Baseline 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 it retrieves real-time market data for A-shares and Hong Kong stocks, listing key fields like latest price and change. It distinguishes from many sibling tools by specifying real-time quotes and mentioning multi-source failover, but lacks explicit contrast with similar tools like stock_batch_realtime or stock_prices.

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 on when to use this tool versus alternatives. The description does not mention scenarios, exclusions, or related tools. An agent would have no context to distinguish from siblings like stock_batch_realtime for batch queries or stock_prices for historical data.

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