stock_zh_a_spot

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint and destructiveHint=false. The description adds a genuinely useful operational note beyond that: repeated invocation gets the caller's IP temporarily blocked by Sina. This is exactly the kind of context annotations don't carry. It does not describe pagination or field coverage, keeping it short of a 5.

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?

Short and front-loaded, with the rate-limit caveat prominent. The docstring-style ':return:'/' :rtype:' lines repeat the first sentence's meaning, which is mild redundancy, but overall it is tight.

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?

There is no output schema, but the description states the return is all A-share real-time quotes as a pandas.DataFrame, and flags the rate-limit risk. For a zero-parameter data-fetch tool this is adequate, though it doesn't say what columns/fields come back.

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 zero parameters, so the baseline is 4. There is nothing for the description to clarify beyond the absent input surface.

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 a specific verb+resource: real-time spot quotes for all A-shares from Sina Finance. Clear enough for an agent to know what it returns. However, it does not distinguish this from the many sibling spot tools (stock_zh_a_spot_em, stock_zh_a_spot_tx, stock_sz_a_spot_em, etc.), so an agent cannot tell which source/scope to pick.

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 the parallel _em/_tx/sz_a spot variants. The only usage-adjacent statement is a rate-limit warning, which is a behavioral note, not when-to-use guidance. An agent has to infer selection criteria on its own.

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