zhiqi_register

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

无注解，描述承担全部披露责任。它披露了私钥在本机生成且不上传（隐私关键点），但未说明操作是否幂等、重复调用的后果、是否需要权限或是否可逆。部分透明但不够全面。

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?

对于单参数、无输出模式的激活工具，描述覆盖了核心行为、身份码格式和私钥安全性。但未提及重复调用是否允许、错误情况或激活后的后续操作，略有不完整，但整体足够。

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?

模式覆盖率为100%，参数activationCode已在模式中描述为'平台Web端创建的待激活身份所返回的激活码'。描述未对参数添加额外语义，基准分为3。

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?

描述使用明确动词'激活'和资源'智能体身份'，并具体说明激活后的结果（唯一身份码格式、绑定责任主体）。与兄弟工具如zhiqi_reissue、zhiqi_retire明显区分，没有歧义。

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.