stock_yzxdr_em

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds the source URL, the date parameter's meaning, and the return type (pandas.DataFrame), which is useful, but it does not disclose additional behavioral traits such as output columns, pagination, or potential rate limits.

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 compact, consisting of a title line, source URL, and a docstring with param/return info. Each line serves a purpose, though the URL might be redundant for an AI agent. It is well-structured and contains no unnecessary fluff.

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 tool with one optional parameter and no output schema, the description provides the source, parameter meaning, and return type. However, it does not detail the output columns or the exact nature of the '一致行动人' data, which could be important for an agent to correctly interpret the results.

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 input schema has zero parameter descriptions, so the description must compensate. It explains the date parameter as '每年的季度末时间点' (year-end quarter end time point) with type str, adding meaning beyond the schema's bare type definition. However, it does not specify the exact date format or allowed values beyond the default '20240930'.

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 resource as 一致行动人 (concerted action persons) from East Money's data center, and includes the source URL. It distinguishes this tool from siblings by naming the specific dataset, though it lacks an explicit verb like 'retrieves' or 'queries'.

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 only contextual hint is the parameter description '每年的季度末时间点' (year-end quarter end time point), but there is no explicit discussion of appropriate use cases or exclusions compared to other stock_* tools.

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