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

Since no annotations are provided, the description carries the full burden and does well: it discloses the PRO subscription requirement, the 403 error behavior, the mutual exclusivity of trade_date versus start/end_date, and the return format. It does not mention rate limits or pagination, but for a read-only data tool the disclosed traits are adequate.

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 structured with an Args/Returns format, making it easy to scan. The opening phrase is a fragment rather than a full sentence, but every part conveys essential information: purpose, subscription requirement, parameters, and return fields.

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?

The description provides return field names and parameter constraints, but it is ambiguous whether a symbol is required or if queries without a symbol are valid, since all parameters are optional in the schema. The tool's query modes are not fully specified, which could lead to incorrect invocation.

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's Args section exactly repeats the parameter descriptions already present in the input schema (100% coverage). The description adds no new meaning beyond what the schema provides, so the baseline score of 3 is appropriate.

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 providing Dragon-Tiger List (龙虎榜) individual stock market data, and the return fields clarify it is a data retrieval tool. However, it lacks an explicit verb like 'get' or 'list' and does not distinguish itself from sibling tools such as top_inst or limit_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?

The description gives no guidance on when to use this tool versus alternatives. It only mentions the PRO subscription requirement and a 403 error for lower tiers, which is a prerequisite, not usage guidance or exclusions.

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