get_limit_down_pool

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

With no annotations, the description carries the full burden, and it does reasonably well: 'Fetches' signals a read-only query, the data source (Eastmoney via Akshare) is disclosed, and the returned columns are enumerated. It omits any statement about return size, rate limits, or behavior for non-trading dates, keeping it short of a 5.

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?

Front-loaded purpose followed by clearly labeled Args and Returns sections; nothing is buried. The second sentence ('Returns detailed list of stocks hitting daily lower price limit') largely restates the first, a small redundancy in an otherwise efficient block.

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 zero-required-parameter read tool with no output schema, the definition supplies the key return fields (代码, 名称, 涨跌幅, 最新价, 成交额, 流通市值) and full parameter documentation. Missing edge-case behavior on dates and absent any sibling cross-reference keep it from being fully complete.

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 0%, so the description must document all three parameters—and it does: date format 'YYYYMMDD' with today as default, top_n default 30, and format options markdown/json/csv default markdown (notably the enum is absent from the schema, so the description is the only source). It does not clarify whether date must be a trading day or what happens on a non-trading day.

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?

States a specific verb and resource ('Fetches limit down stocks pool (跌停股池)') and reinforces it with 'stocks hitting daily lower price limit', so the tool's purpose is unambiguous. It does not explicitly contrast itself with close siblings like get_limit_up_pool, get_limit_up_down, or get_market_pool_details, which a 5 would require.

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?

Usage is only implied: a reader infers this returns today's (or a given date's) limit-down pool, and that date defaults to today. There is no explicit when-to-use/when-not, and no routing hint toward the overlapping siblings get_limit_up_down or get_market_pool_details.

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