stock_zh_ah_spot_em

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the source URL and the return type (pandas.DataFrame), which is useful but minimal. It does not disclose additional behavioral traits like rate limits, data freshness, or scope of the returned data. No contradiction with 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?

The description is short but contains redundancy: the first line and the ':return:' line are essentially identical. The URL and ':rtype:' add some structure, but the repeated phrase makes it less concise than it could be. It is a mix of a title, URL, and docstring-style return information without a clear front-loaded summary.

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 real-time quote tool, the description provides the data source and return type, which is somewhat helpful. However, since there is no output schema, the description could explain more about the returned data, such as the list of AH stocks or columns. It does not mention whether this is a full snapshot or if any filtering applies, leaving some ambiguity for the agent.

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 has zero parameters, so the schema fully covers parameter semantics (vacuously at 100%). Per the rubric, a baseline of 4 is appropriate for 0 params, and the description does not need to add parameter details. The description provides no parameter information, which is fine since none exist.

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 identifies the tool as returning AH share price comparison real-time quotes from East Money (东方财富网). The included URL and the word '实时行情' (real-time quotes) specify the resource and type of data. It distinguishes from similar siblings like stock_zh_ah_daily (historical) and stock_zh_ah_spot (likely a different source) through the _em suffix and East Money URL, though it lacks an explicit verb like 'get' or 'fetch'.

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 provides no guidance on when to use this tool versus alternatives such as stock_zh_ah_spot, stock_zh_ah_daily, or stock_zh_ab_comparison_em. It does not state any context, prerequisites, or exclusions. The only clue is the East Money URL, which is not explicit usage guidance.

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