stock_dzjy_yybph

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is clear. The description adds the allowed symbol choices and pandas DataFrame return type, but no further behavioral details such as pagination or request behavior.

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 and front-loaded with the Chinese title, followed by a URL and docstring. Every sentence serves a purpose with 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 simple tool with one parameter, the description covers parameter choices and return type. It lacks column details or a more precise description of the ranking data, but is adequate given the simplicity and no output schema.

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 schema has one 'symbol' parameter with no description or enum, and schema coverage is 0%. The description compensates by explicitly listing all valid choices: 近一月, 近三月, 近六月, 近一年, which is essential for correct invocation.

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 a block trade business department ranking from East Money's data center, with a URL and return type. It distinguishes from sibling block trade tools by scope, but lacks an explicit verb such as '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?

No guidance on when to use this tool versus other block trade tools like stock_dzjy_mrmx. The description only provides the data source and parameter choices, with no alternatives, exclusions, or usage context.

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