stock_zh_a_hist_min_em

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

Annotations already declare readOnlyHint=true and destructiveHint=false, which convey safety. The description adds the data source (Eastmoney) and return type (pandas.DataFrame) but does not disclose additional behaviors like pagination, rate limits, or data granularity beyond the period parameter.

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 a compact docstring with a URL, parameters, and return type. It is reasonably concise, but the URL and repetitive type annotations add some clutter. It is front-loaded with the main purpose, which helps readability.

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, and the description only states '每日分时行情' and 'rtype: pandas.DataFrame' without describing the DataFrame's columns or indexing. It also lacks context on limitations, such as data frequency or potential web scraping issues, leaving important information for a tool with no structured output definition.

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 description coverage is 0%, so the description compensates by detailing each parameter, including period choices ('1','5','15','30','60') and adjust choices ('', 'qfq', 'hfq'). It also states parameter types (str), adding meaningful semantic information beyond the bare schema.

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 daily intraday quotes (每日分时行情) for A-shares from Eastmoney, with a specific verb and resource. It distinguishes itself from daily historical tools like stock_zh_a_hist by its focus on minute-level data, though it does not explicitly mention alternatives.

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 is provided on when to use this tool versus alternatives. The description lacks any mention of use cases, exclusions, or comparisons to related tools such as stock_zh_a_hist or stock_zh_a_minute, leaving the user to infer the appropriate context.

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