stock_zt_pool_strong_em

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds only the source URL and the fact that the return is a pandas DataFrame, but does not disclose any additional behavioral aspects such as data limitations, update frequency, or error handling. 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 brief and direct, providing the source, parameter, and return type in a compact docstring format. The URL is arguably unnecessary for an AI agent but not overly verbose. It is well-structured but lacks narrative context.

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?

While the tool is simple, the description does not explain what qualifies as a 'strong stock' within the limit-up pool, nor does it differentiate from other zt_pool tools like stock_zt_pool_em, stock_zt_pool_zbgc_em, or stock_zt_pool_sub_new_em. An agent could not confidently select this tool without additional context. The rich annotations partially compensate, but the description leaves selection criteria unclear.

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 description documents that the 'date' parameter is a trading day (交易日) and the return is a DataFrame, adding some meaning beyond the schema's type/default. However, it does not specify the expected date format (e.g., YYYYMMDD) or allowed range, leaving ambiguity for an agent.

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 identifies the tool as East Money's 'strong stock pool' under limit-up quotes, with a URL and return type. It clearly states the data source and what is returned, but lacks an explicit verb (e.g., 'fetches') and does not distinguish this pool from other limit-up pool tools in the sibling list.

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 given on when to use this tool over alternatives. The description only provides a URL and docstring, with no mention of use cases, exclusions, or comparison to sibling tools like stock_zt_pool_em or stock_zt_pool_zbgc_em.

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