ncloud_serverless_create_user

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

在仅有 destructiveHint=false 的注解下，描述额外披露了 POST 异步语义（202 Operation）以及重名冲突会返回 409，这些对创建类工具很有价值。但没有提及权限要求、认证方式或返回的 Operation 如何进一步查询，仍有一些行为空白。

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?

一句话包含操作、端点和关键状态码，没有冗余信息，信息密度高且便于 agent 快速解析。

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?

对于无输出 schema、注解较少的创建工具，描述给出了异步接受（202）和冲突处理（409），配合 schema 参数说明基本支持一次正确调用。缺少对 Operation 轮询或集群不存在错误的提示，但整体没有重大缺失。

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，而 schema 已覆盖 password、permission、clusterName 三个参数；描述本身没有补充参数含义，只在端点中重复了 {clusterName}。name 参数缺乏说明，描述也没有为此弥补，因此价值有限。

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?

描述以明确的动词“Create”和资源“DB user”开头，并给出具体端点 POST /mysql/v1/clusters/{clusterName}/users，能够与同组的 list/get/update/delete_user 清晰区分。工具名和描述一致，agent 可以准确判断这是单用户创建操作。

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?

通过“Create a DB user”可以推断应在新建数据库用户时调用，409 提示也隐含了“重名不可创建”的边界，但描述没有显式说明与 ncloud_serverless_batch_create_users、update_user、delete_user 等替代工具的选择关系，也没有给出集群必须存在等前置条件。属于隐含用法而非明确的路由指导。

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