get_dragon_tiger_list

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

Annotations already declare readOnlyHint=true, so the read-only nature is covered. The description adds the return fields (上榜个股, 上榜原因, 买入/卖出总额), which is useful context, but does not disclose any additional behavioral traits such as pagination, ordering, or limits. 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 a single, front-loaded sentence with a clear verb and resource, followed by the relevant scope and return details. Every phrase carries information and there is zero waste.

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 2-parameter, read-only list tool with good annotations, the description is mostly complete: it explains the purpose, date range, and return content. However, since there is no output schema, a brief note on return format or potential limitations (e.g., result limits) would be beneficial. Minor gap.

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 coverage is 100%: both startDate and endDate have clear descriptions with format examples. The description's '按日期范围' only restates what the schema already conveys, adding no extra meaning beyond the structured parameter info.

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 starts with a specific verb '获取' (get) and resource '龙虎榜详情列表' (Dragon-Tiger list details), scoped by date range '按日期范围'. It also lists the returned contents (listed stocks, reasons, buy/sell totals), which clearly distinguishes it from sibling tools like get_dragon_tiger_stats (stats) and get_dragon_tiger_seat_detail (seat details).

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 date range scoping implies when to use it, but there is no explicit guidance on when to choose this tool over its siblings (e.g., get_dragon_tiger_stats, get_dragon_tiger_seat_detail). No exclusions or alternative recommendations are provided, so usage guidance is only implied.

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