stock_zh_kcb_spot

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

Annotations already declare readOnly/openWorld/idempotent/non-destructive, so safety is covered. The description adds genuinely useful context beyond them: a rate-limit/IP-ban warning for bulk scraping and the return type (pandas.DataFrame), which matters since there is no output schema.

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?

Front-loaded and brief, with the source, warning, and return type all packed into a few lines. The raw docstring fragments (:return:, :rtype:) and trailing URL are slightly untidy but cost little space.

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 zero-parameter snapshot tool with no output schema, the description covers source, scope, the rate-limit risk, and the return type — enough to invoke it correctly. It stops short of saying which columns/fields the DataFrame contains, and gives no basis for picking it over the equivalent Eastmoney sibling.

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 no arguments (0 parameters), so there is nothing for the description to compensate for. Baseline 4 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?

States the resource precisely — real-time STAR Market (科创板) quotes from Sina Finance — which combined with the name makes the retrieval action unambiguous. It does not, however, distinguish itself from the very similar sibling stock_kc_a_spot_em (same board, different source), so an agent has no stated basis for choosing between them.

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 when-to-use guidance and no alternative named, despite at least one near-identical sibling (stock_kc_a_spot_em) and a historical counterpart (stock_zh_kcb_daily). The only stated condition is a caveat about heavy scraping, which is a warning rather than usage routing.

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