setup_email_account

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

没有任何 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?

整句仅一句话，信息密度高且先给出主行为再说明自动配置能力，没有冗余内容。但过于简短导致行为细节缺失，所以未给5分。

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?

该工具涉及账号配置和凭据处理，且没有 output schema 说明调用结果，也没有 annotations 覆盖安全性。描述缺少返回/结果形式、配置生效范围、与 configure_email_server 的分工等关键上下文，代理难以判断调用后的状态。

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?

input schema 对 3 个参数均有 description，覆盖率为 100%，因此基础分为 3。描述中的“自动识别邮箱类型并配置服务器”与 schema 中 provider 的“不填写则自动识别”语义一致，但未额外补充参数格式、约束或交互关系。

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?

描述使用明确动词“设置”和宾语“邮箱账号”，并补充了“自动识别邮箱类型并配置服务器”这一核心行为，代理能知道该工具做什么。但与兄弟工具 configure_email_server 存在语义重叠，未做区分，因此不到5分。

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?

描述没有说明何时该用本工具而不是 configure_email_server、list_supported_providers 或 test_email_connection。也没有给出前提条件（如是否需要授权码、是否必须先列出支持提供商）。代理只能靠猜测选择工具。

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