get_zt_pool

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

注解已声明 readOnlyHint=true 和 openWorldHint=true，描述未与其矛盾，并补充了股池类型和日期查询等行为信息。未涉及输出结构、分页或权限，但注解已覆盖安全属性，因此达到基线。

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?

描述为一句紧凑的话，前置核心功能，后接股池类型和历史查询能力，无冗余信息，结构清晰。

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?

工具逻辑简单（2个可选参数，无输出 schema），描述加 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?

Schema 对两个参数的描述覆盖率为100%，描述中列举的股池类型与 schema 中 enum 的说明重复，未增加额外语义。符合 schema 承担主要解释责任时的基线评分。

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?

描述以'获取'开头，明确资源为'涨停股池数据'，并列出6种股池类型（涨停、昨日涨停、强势、次新、炸板、跌停），与兄弟工具（如资金流、龙虎榜）明显区分。语义具体、无歧义。

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?

描述说明可指定日期查询历史，暗示默认不复用参数，但未明确说明何时适合使用或排除其他工具。由于兄弟工具中没有类似的涨停池工具，上下文清晰，足以引导使用。

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