stock_individual_spot_xq

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

No annotations provided, so description must disclose behavioral traits. It only states the function without mentioning read-only nature, required permissions, rate limits, or error behavior. For a data retrieval tool, safety and idempotency are not addressed.

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?

Single concise sentence that is front-loaded with action and resource. No redundant information; every word serves a purpose.

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?

Lacks output schema and does not describe return data fields, real-time vs delayed, or error handling. For a tool with one parameter, basic completeness would include what the returned data looks like.

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%, so baseline is 3. Description adds value by including example stock codes (SZ600246, SH600000), clarifying the expected format beyond the schema's generic '股票代码' description.

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?

Description states specific verb '获取' (get), resource '个股实时行情数据' (individual stock real-time market data), and source '雪球' (Xueqiu). This clearly distinguishes it from sibling tools like stock_zh_a_spot_em which target different sources.

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?

Description implies usage for Xueqiu-sourced real-time data but provides no explicit guidance on when to use vs alternatives (e.g., realtime_quote, stock_hk_spot_em). No when-not-to-use or prerequisites stated.

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