tmall_save_account

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?

工具操作简单，无输出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%，已说明每个参数的含义（username店铺账号，password登录密码，shopName店铺名称）。描述未额外补充参数语义，基线为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?

描述明确说明'保存店铺账号（不登录，仅保存）'，动词+资源清晰，并强调与登录的区别，能有效区别于tmall_login等兄弟工具。

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?

描述暗示了使用场景（仅保存，不登录），但未明确说明何时使用此工具而非tmall_login。虽然语境清晰，但缺少明确的排除性指引。

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