获取自选基金

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

注解已标明 readOnlyHint=true、idempotentHint=true、destructiveHint=false，描述与之一致，无矛盾。描述补充了默认分组和查看他人等调用行为，但未超出注解已覆盖的安全特性。

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?

描述三句话，直接说明功能、返回值、支持他人查看，并给出获取 pid 的建议。结构紧凑，无冗余信息。

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?

在已有输出模式和注解的情况下，描述涵盖了调用所需的前置步骤、默认参数行为和可选参数含义。对于该工具的简单查询场景，信息足够完整。

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?

输入模式中 pid 和 user_id 均有详细描述，包括默认值、常用取值、获取途径和可选性。工具描述进一步建议使用 get_watchlists 获取 pid，参数含义完整清晰。

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?

明确说明获取自选基金分组下的基金列表，并返回代码、名称、目标仓位。与获取股票列表的 get_watchlist_stocks 区分，且支持他人视角，目的清晰。

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?

给出使用前置条件：建议先用 get_watchlists 或 get_user_watchlists 获取 pid，并说明默认 -110 和常用分组。虽未明确排除其他替代工具，但提供了足够的调用时机和参数准备指引。

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