连板潜力股-最新一份

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

No annotations are provided, so the description carries the behavioral disclosure burden. '返回 reports.db 中最新一份...' implies a read-only retrieval of a stored report, which is helpful, but it does not mention empty-result behavior, output shape, or whether the result is cached. For a zero-parameter getter this is acceptable but not rich.

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 compact sentence, front-loaded with the action and resource, and the parenthetical adds relevant usage context without redundancy. Every word earns its place.

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 zero-parameter, read-only retrieval tool with no output schema, the description is nearly complete: it names the source database, the selection criterion (latest), and the intended audience. The main gap is not describing the returned fields or what happens when no report exists, but the tool's simplicity keeps this gap minor.

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 parameters and 100% coverage, so the baseline is 4. The description adds context about what the no-argument call returns—the latest limit-up scan result from reports.db—but there is no parameter-specific semantic burden to satisfy.

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 uses a specific verb (返回), identifies the resource (reports.db 中最新一份连板扫描结果), and adds a use context (前端登录看板用). It is clear about what is returned, though it does not explicitly name sibling tools such as limit_up_scan or limit_up_calibration_latest to differentiate them.

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 parenthetical '前端登录看板用' gives a clear intended use context, suggesting this is for dashboard display of the latest precomputed scan rather than running a new scan. However, it does not explicitly state when not to use the tool or mention alternatives among the many report/scan-related siblings.

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