删除子账号

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

Annotations already declare destructiveHint=true, so the description's addition of '不可恢复' (irreversible) provides extra specificity beyond the annotation. However, it does not mention the confirm_token flow or any other side effects, which is a notable behavioral aspect left to the schema. The description adds some value but not rich behavioral context.

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?

The description is two short sentences with the crucial warning (irreversible) front-loaded, and no redundant information. It is appropriately sized for a simple deletion tool.

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?

The description is adequate for a straightforward deletion tool, but it omits mentioning the confirm_token behavior (e.g., whether a confirmation step may be required) and does not explicitly note the single-item scope versus batch alternatives. However, the schema covers these details, so the description is not critically incomplete.

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 description coverage is 100%, so all parameters (id, product, confirm_token) are already documented. The description does not add any parameter-specific meaning beyond what the schema provides, so the baseline of 3 applies.

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?

The description clearly states the action ('删除动态住宅的一个子账号' - delete a sub-account of dynamic residential) and explicitly notes irreversibility, distinguishing it from batch operations like sub_account_delete_batch. It is specific with verb and resource.

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?

There is no guidance on when to use this tool versus alternatives, such as sub_account_delete_batch, or any prerequisites or conditions. The description only states the basic function, leaving the agent to infer usage context from the tool name and schema.

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